J. Chad Bourque writes:
> Just a thought, but can you get all memory variables and objects you
> deal with into a few references? As in have everything hang off of an
> app object or maybe a few app objects. If so, you can do a
> _Screen.AddProperty() (or AddObject() if you prefer)to hold references
> to your stuff. Then, you can issue CLEAR ALL ad nauseam and it won't
> affect anything on the _Screen object (including what you add to it).
> Then, at the end of your program, just remove the properties/objects
> (good programmer) or let VFP just not add them back on next restart (BA=
D
> programmer <s>).
Hmmm... so stuff attached to _SCREEN is never cleared? Never? If that's=
=20
true, then yes I could attach to _SCREEN instead of declaring public=20
variable references.
The objects I'm instantiating are timers, and they have the smarts to com=
mit=20
suicide when their tasks are complete (good programmer?).
Thanks Chad... assuming I'm relatively protected by attaching to _SCREEN,=
=20
your idea should work. It still feels pretty draconian to issue CLEAR AL=
L=20
all over the place, but it is another option. I don't like releasing=20
something that when run could screw up somebody's setup.
--=20
Paul McNett
Liberal Earthling
©2003 Paul McNett |
