From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,99f33f51845a7793 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-11-22 03:37:52 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!cleanfeed.casema.net!leda.casema.net!bnewspeer01.bru.ops.eu.uu.net!bnewsifeed03.bru.ops.eu.uu.net!lnewspost00.lnd.ops.eu.uu.net!emea.uu.net!not-for-mail From: "David Crocker" Newsgroups: comp.lang.ada References: <3be27344$0$227$ed9e5944@reading.news.pipex.net> <3BE42900.7590E899@adaworks.com> <3be65f4c$0$237$ed9e5944@reading.news.pipex.net> <3BF6E4DF.FA47ACDB@adaworks.com> <3BF93F0F.D5E4D0B7@Raytheon.com> <3BFA6BDC.26E7557E@Raytheon.com> <3bfa84ca$0$8514$ed9e5944@reading.news.pipex.net> Subject: Re: 'withing' problem [code generation] Date: Thu, 22 Nov 2001 11:42:59 -0000 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Message-ID: <3bfce38e$0$8512$ed9e5944@reading.news.pipex.net> NNTP-Posting-Host: andrew.imsltd.com X-Trace: 1006429070 reading.news.pipex.net 8512 194.202.27.87 X-Complaints-To: abuse@uk.uu.net Xref: archiver1.google.com comp.lang.ada:16847 Date: 2001-11-22T11:42:59+00:00 List-Id: No, Java's solution has nothing to do with the fact that Java non-primitive types are reference types. It has everything to do with the compiler being flexible enough process declarations in whatever order necessary to perform type checking without needing forward declarations. Our own language (see www.eschertech.com) does not treat non-primitive types as reference types, and we also allow forward-referencing of and circular depedencies between types. It does mean that you need at least a 2-pass compiler, but the days when this meant physically reading the source twice are long gone. -- David Crocker, Escher Technologies Ltd. www.eschertech.com "Mark Lundquist" wrote in message news:B8zK7.51483$XJ4.30270717@news1.sttln1.wa.home.com... > > "David Crocker" wrote in message > news:3bfa84ca$0$8514$ed9e5944@reading.news.pipex.net... > > > > The nicest solution is the one used by Java (and by our own product) - no > > restriction at all on forward referencing classes/types, or on packages > > referring to each other (except for absurd cases like 2 classes inheriting > > from each other). This is the way all programming languages should go, > IMO. > > OK -- but isn't Java's solution more of just a side-benefit of being a > by-reference language? > > It seems like there are some underlying trade-offs :-) > > Cheers, > -- Mark Lundquist > http://members.home.com/mlundquist2/consulting > > >