Re: PCODE Interpereters 101

Sam Roberts <sam@cogent.ca>
12 Feb 1999 02:59:05 -0500

          From comp.compilers

Related articles
PCODE Interpereters 101 carld@td.co.nz (Carl Dawson) (1999-01-22)
Re: PCODE Interpereters 101 dwighth@ipa.net (Dwight Hughes) (1999-01-23)
Re: PCODE Interpereters 101 sda@rt66.com (1999-01-31)
Re: PCODE Interpereters 101 tgl@netcom.com (Tom Lane) (1999-02-03)
Re: PCODE Interpereters 101 sda@rt66.com (1999-02-05)
Re: PCODE Interpereters 101 gneuner@dyn.com (1999-02-05)
Re: PCODE Interpereters 101 cfc@world.std.com (Chris F Clark) (1999-02-10)
Re: PCODE Interpereters 101 sam@cogent.ca (Sam Roberts) (1999-02-12)
Re: PCODE Interpereters 101 kevin.b.smith@intel.com (Kevin B. Smith) (1999-02-15)
Re: PCODE Interpereters 101 cfc@world.std.com (Chris F Clark) (1999-02-15)
Re: PCODE Interpereters 101 toring@inet.uni2.dk (Torben Ring) (1999-02-18)
Re: PCODE Interpereters 101 aduncan@cs.ucsb.edu (aduncan) (1999-02-21)
Re: PCODE Interpereters 101 albaugh@agames.com (1999-02-24)
Re: PCODE Interpereters 101 Scott.Daniels@Acm.Org (Scott.David.Daniels) (1999-03-02)
| List of all articles for this month |
From: Sam Roberts <sam@cogent.ca>
Newsgroups: comp.compilers
Date: 12 Feb 1999 02:59:05 -0500
Organization: Cogent Real-Time Systems Inc.
References: 99-01-079 99-01-117 99-02-008 99-02-019 99-02-050
Keywords: Pascal, code, design

Chris F Clark <cfc@world.std.com> writes:


> > Actually, displays can be very efficient at the procedure call point.
>
> > My main axe these days is C++ and I often have a situation where I
> > would use lexical nesting if I could.
>
> Actually, the solution in C++ is to make an "object" out of the
> variables you want as your enclosing scope. All of your nested
> functions them are members of that. It gives you efficient access to


This is discussed at length and with examples, I believe, in Coplien,
Advanced C++ Programming styles and Idioms, Addison-Wesley.


Sam
--
Sam Roberts (sam@cogent.ca), Cogent Real-Time Systems (www.cogent.ca)


Post a followup to this message

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