Creating a list before including GW.bas the users get in trouble! In the hope nobody create a list before, you use listpointers with constants. I do not critisize that, because you have sure your reasons, but that should be described in API reference and Cheat Sheet. Or have I overread it.
Post subject: Re: Creating a List Before Including GW
Posted: Sat Dec 03, 2016 5:42 pm
Joined: Tue Jan 03, 2012 9:31 am Posts: 5485 Location: Paris, France
This is the internal machinery of GW, it wouldn't be a layer of indirection but a contrario a simplification.
I'm not very fond of adding a warning, where put it? how technical should it be? I don't see how to keep it simple, I can't just say "don't create any list before calling include GW.bas" without explaining why, can I ?
By another layer of indirection I mean access to the lists would become more indirect and this would degrade performance. But I agree that things would become cleaner, so if the price is not too high maybe it will be worth doing. Anyway, to further reduce the risk of clashes in case there are bundle creations before INCLUDE "GW.bas", or in case other keys are used by someone else in the global bundle, I would suggest: 1. Change all the initial BUNDLE.PUT global, ... into: BUNDLE.PUT 1, ...
2. Add the prefix "gw_" in front of all the keys of the global bundle.
Users browsing this forum: No registered users and 1 guest
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum