Re: Order of argument evaluation in C++, etc.

hbaker@netcom.com (Henry Baker)
Wed, 30 Aug 1995 04:32:06 GMT

          From comp.compilers
Related articles
[42 earlier articles]
Re: Order of argument evaluation in C++, etc. daniels@cse.ogi.edu (1995-08-24)
Re: Order of argument evaluation in C++, etc. pardo@cs.washington.edu (1995-08-25)
Re: Order of argument evaluation in C++, etc. hbaker@netcom.com (1995-08-25)
Re: Order of argument evaluation in C++, etc. jan@neuroinformatik.ruhr-uni-bochum.de (1995-08-25)
Re: Order of argument evaluation in C++, etc. stefan.monnier@epfl.ch (Stefan Monnier) (1995-08-28)
Re: Order of argument evaluation in C++, etc. chase@centerline.com (1995-08-28)
Re: Order of argument evaluation in C++, etc. hbaker@netcom.com (1995-08-30)
| List of all articles for this month |
Newsgroups: comp.compilers
From: hbaker@netcom.com (Henry Baker)
Keywords: C++, optimize
Organization: nil organization
References: 95-07-068 95-08-195
Date: Wed, 30 Aug 1995 04:32:06 GMT

jthill@netcom.com (Jim Hill) writes:
>
> Unless I'm very much mistaken, alias identification is an insoluble
> problem, and flagging order dependencies in expressions runs straight into
> that wall.


There's a particularly important special case that's not only soluble --
it's also trivial. These are objects whose reference counts are exactly
one -- so-called 'linear' objects -- and a type system can easily keep
track of linear objects.


See also


ftp://ftp.netcom.com/pub/hb/hbaker/Use1Var.html (also .ps.Z)
ftp://ftp.netcom.com/pub/hb/hbaker/ForthStack.html (also .ps.Z)


--
www/ftp directory:
ftp://ftp.netcom.com/pub/hb/hbaker/home.html
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.