Hi
I understand, but before we start implementing something brand new native, which BTW leads quite far away as far I can see it, even my simple proposed method can be used without too much concern, and even it can be used by 3rd party libs to provide such singletons, or whatever we call it. AFAICS it's nothing more than a variable (or function) accessible by all program modules with some value, in this case, it's a single instance class.
Yes Victor, I see your point. I insisted on a deeper aproach because I was hoping the discussion would reach issues like singleton inheritance, but now I understand it's not a convenient discussion for now.
If anything, Harbour may support single instance classes natively to help this case, and this is probably possible to add without deep changes, but I'm not sure we should add a brand new base variable type/scope/implementation until we know all the benefits which this can give us over already existing methods.
Ok.
Few of us have proposed solutions, it'd be nice if you could comment on them.
Oops! Sorry, I thought I was doing that! Thank you Regards Leandro Damasio _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
