home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.misc
- Path: sparky!uunet!decwrl!pa.dec.com!rdg.dec.com!jch
- From: jch@rdg.dec.com (John Haxby)
- Subject: Re: Pointers
- Message-ID: <1992Nov12.103513.14043@rdg.dec.com>
- Sender: news@rdg.dec.com (Mr News)
- Organization: Digital Equipment Corporation
- References: <92Nov10.125426est.47525@neat.cs.toronto.edu> <BxIoDv.72J@mentor.cc.purdue.edu> <1992Nov11.155149.14744@rdg.dec.com> <1992Nov12.081454.23507@jyu.fi>
- Date: Thu, 12 Nov 1992 10:35:13 GMT
- Lines: 30
-
- In article <1992Nov12.081454.23507@jyu.fi>, sakkinen@jyu.fi (Markku Sakkinen) writes:
- |> In article <1992Nov11.155149.14744@rdg.dec.com> jch@rdg.dec.com (John Haxby) writes:
- |> > ...
- |> >In CLU, you can pass paramaters of type PROCTYPE to accomplish exactly
- |> >the same thing, or you can use type parameterization (genericism if you like)
- |> >for a similar mechanism for, often, much the same purpose. CLU doesn't
- |> >have references, yet alone pointers.
- |> > ...
- |>
- |> Actually, I think, _all_ variables in CLU are references,
- |> except those of atomic types. (Pretty much like LISP.)
-
- CLU has only two flavours of cluster: mutable and immutable.
- Procedure (and iterator) parameter passing is by sharing (rather than
- value or reference) since there is no notion of value or reference, only
- of the name of an object which may be one of many names.
-
- The implementation uses pointers left, right and centre for practically
- everything -- the exceptions might be int, char, bool and possibly float.
- For the VAX implementation, the native VAX implementation--the
- language is not interested in grubby pointers and references, only in names.
-
-
- --
- John Haxby, Definitively Wrong.
- Digital <jch@rdg.dec.com>
- Reading, England <...!uknet!wessex!jch>
-
- ----------------------------------------------------------------
- The opinions expressed herein are my own, not my employers.
-