Re: Weighing in on everything
- Posted by irv mullins <irvm at ellijay?c?m> Apr 27, 2008
- 831 views
Matt Lewis wrote: > Good, working namespaces are now in there. The current debate is about the > syntax, but not the functionality, except for the default namespace thing, > but that's just a little nice to have thing, that may or may not be a good > idea. I don't think we've explored that enough. Make that 'pretty good' - if you're referring to the svn version, not stock eu. At least now globals are visible thruout the include chain. What's needed now is some way for an include file to make and pass on 'copies' of included variables. To give an example: Windows controls have lots of things in common: height, width, text color, background color, border, title/text, etc... Windows has lots of controls - windows, buttons, labels... most of which use all the "things in common" listed above. However, you can't get by with ONE height or ONE width for all buttons and windows in your program. That's what you get now if you try to include the "things in common" file in both your window.e and button.e files. Sure, it sort of smells like objects, so some will be against it, but it certainly would help the rest of us if window:height and button:height were separate items without having to repeat the "things in common" code over and over again. Such a thing is possible - it was done by accident a few years ago. Despite protests, Rob 'fixed' that. Probably he was worried about unexpected consequences, I can understand that. Perhaps it's time to give that another look, to see if there really are any disastrous side effects. If people are worried about this, why not just another keyword - import - perhaps, which works like include but creates copies instead of bringing in the original? If people don't use "import", they won't have anything to worry about.