|
Post by Carl Gundel on Dec 4, 2020 22:35:15 GMT -5
Honestly, I prefer it like that. Gives it a semblance of encapsulation from OO programming, and it makes sense. Each "module" is responsible for it's own stuff, and the other modules can't interfere. I agree with this line of thinking. In fact this is intended to be a sort of simple object oriented mechanism, not so much as to call LB5 an OOP language, but to give users a very easy to understand objects-lite mechanism. With a little thought some clever things can be done without learning a whole new way of programming.
|
|
jordi
Full Member
A simple solution is the smarter one.
Posts: 106
|
Post by jordi on Dec 5, 2020 1:54:25 GMT -5
Maybe a function to getGlobal or setGlobal. Another solution is to have a Globals file, and each module loads that file with a command like loadGlobals #file
|
|