Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!wuarchive!uunet!igor!yoda!jls From: jls@yoda.Rational.COM (Jim Showalter) Newsgroups: comp.lang.ada Subject: Re: procedural variables Message-ID: Date: 20 Feb 91 21:02:26 GMT References: <9102110959.aa23851@PARIS.ICS.UCI.EDU> <662@esosun.UUCP> <24590@neptune.inf.ethz.ch> <2834@cod.NOSC.MIL> <1991Feb16.141232.1@elcgl.epfl.ch> <88642@tut.cis.ohio-state.edu> Sender: news@Rational.COM Lines: 13 Agreed: table-driven programming requires subprogram variables to work smoothly. We encounter other cases where they would be quite useful. By the way, we implemented subprogram variables when we wrote our Ada-based X bindings. Works quite well, and only requires the body of one package to be rehosted on each platform. The rest is pure Ada. -- ***** DISCLAIMER: The opinions expressed herein are my own. Duh. Like you'd ever be able to find a company (or, for that matter, very many people) with opinions like mine. -- "When I want your opinion, I'll beat it out of you."