Hi,
Is there a way to have a .p automatically run an internal procedure, much like a destructor, when it is deleted, e.g. after invocation of an internal procedure in a SINGLE-RUN started .p?
Using CREATE WIDGET-POOL will already help in removing any lingering handle based objects (provided they were created in that widget-pool).
A companion OO object that keeps the state of the .p could also be an option, which gets its destructor called when the reference the .p has to it goes out of scope...
Thanks,
Lieven
At one point creating an OOABL single-run facility modeled after the procedural single-run facility was discussed within development. It seems to me that if we supported such a facility, the behavior requested in this post would be available via the class destructor.
Evan Bleicher
Sr. Development Manager
Progress Software
We have used your suggested approach with success: A companion OO object that keeps the state of the .p could also be an option, which gets its destructor called when the reference the .p has to it goes out of scope...
It's not as clean as having a language construct build in off course but it does work reliably.