Related articles |
---|
[25 earlier articles] |
Re: Multiple return values tim@franck.Princeton.EDU (1997-05-04) |
Re: Multiple return values jens.hansson@mailbox.swipnet.se (1997-05-04) |
Re: Multiple return values jamesl@netcom.com (1997-05-08) |
Re: Multiple return values hbaker@netcom.com (1997-05-08) |
Re: Multiple return values mark@omnifest.uwm.edu (1997-05-13) |
Re: Multiple return values bear@sonic.net (Ray Dillinger) (1997-05-13) |
Re: Multiple return values jan@fsnif.neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) (1997-05-14) |
Re: Multiple return values hbaker@netcom.com (1997-05-14) |
Re: Multiple return values markt@harlequin.co.uk (Mark Tillotson) (1997-05-25) |
Re: Multiple return values hbaker@netcom.com (1997-05-25) |
Re: Multiple return values jmccarty@sun1307.spd.dsccc.com (1997-05-30) |
From: | Jan Vorbrueggen <jan@fsnif.neuroinformatik.ruhr-uni-bochum.de> |
Newsgroups: | comp.compilers |
Date: | 14 May 1997 23:56:23 -0400 |
Organization: | Institut fuer Neuroinformatik, Ruhr-Universitaet Bochum, Germany |
References: | 97-05-166 |
Keywords: | design |
mark@omnifest.uwm.edu (Mark Hopkins) writes:
> What's missing that will make everything easier is (a) structured
> expressions, example: { 3, 5, 3, 2 } is a constant of type int [4],
> also convertible to type struct { int; int; int; int; }, or even int
> []. (b) assignments to structured variables, example: {X, Y} =
> IntPair();
All this is in that well-known language, occam2, with the nice
semantic properties Henry Baker mentioned in another post; the
compiler makes extensive use of them for optimization. Also, functions
in occam2 are side-effect free (and the compiler checks that!) and
thus trivially in-lineable etc. Very nice.
Jan
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.