|
Got it. That makes sense. Thanks for the clarification. Tom >--- James Rich <james@eaerich.com> wrote: > I am saying that returning a pointer to private > storage is bad design and > using static to fix that problem continues the bad > design. static has > good uses. Using it to keep your storage around so > you can return a > pointer to it is not one of them. > > James Rich > james@eaerich.com > > >> On Fri, 31 May 2002, Tom Daly wrote: > > Are you suggesting that using STATIC is, as a > general > > principle, poor design? > > > > Suppose the procedure has 'initialization' code > that > > should only be run once, perhaps to open files. > I'd > > want to keep that state in a STATIC variable. __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.