Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!uw-beaver!milton!ogicse!pdxgate!parsely!percy!qiclab!m2xenix!news
From: news@m2xenix.psg.com (Randy Bush)
Newsgroups: comp.lang.modula2
Subject: Re: Standard Modula2
Message-ID: <1991Jan25.174802.11700@m2xenix.psg.com>
Date: 25 Jan 91 17:48:02 GMT
References: <1180.279FE75C@puddle.fidonet.org>
Organization: Pacific Systems Group, Portland Oregon US
Lines: 18

Jon.Guthrie@p15.f20.n226.z1.fidonet.org (Jon Guthrie) writes:

> All I want to do is be able to assign any quantity of type ADDRESS to an
> opaque type.  I also want to be able to test an opaque type for equality to
> NIL.

Sorry to miss your original point and blather on about uninitialized opaque
detection.

You could get dirty and try the old type transfer hack
    OpaqueInstance := OpaqueTypename(address)
and
    OpaqueInstance = OpaqueTypename(NIL)

What you really want is the new TRANSLUCENT type extension which is being
proposed by a subgroup of the BSI.  :-)
-- 
..!{uunet,qiclab,intelhf,bucket}!m2xenix!news