You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
I'll acknowledge your linked page contains things I don't begin to understand; however, I am totally inured to the concept that the programmer is responsible for cleaning up after himself....
...and that the best way to do this is to always "obtain" (create, get, open ) and "release" (close, destroy, free) in the same procedure...making scope moot.
This technique could be very handy if you wish to provide a common module (include) to others.
It can prevent manual cleaning code in your pbmain() for example.
The functions in that module could also be prepared to verify it's properly intitialized and evt. take action.
Since the variant will result in a callback call on clearing, you'll be able to take appropriate action.
I would not use it on severe use like in a windowprocedure, that's to much overhead imo.
However for neat and clean simple include stuff it's very handy.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment