Re: A Problem with v2.4 (for Rob)
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> May 15, 2003
- 419 views
On Wed, 14 May 2003 02:37:25 +0000, Al Getz <Xaxo at aol.com> wrote: Al, the example you gave worked fine, flagging the line of code in your program which now needs a namespace qualifier. The following shows how to get this problem in a way that would force you to edit someone elses code: --Someone else's code: lib1.e is: include subs1.e d() subs1.e is: global procedure d() ?{1} end procedure --Another persons code: lib2.e is: include subs2.e d() subs2.e is: global procedure d() ?{2} end procedure --Your code can then have all the namespace qualifiers you can shake a --stick at, it will always bomb (even with your include twice idea): include lib1.e as x include lib2.e as y What I think is needed is that if you are "inside" an include as statement, then it should automatically select globals defined since that "as" directive over any defined beforehand. You would still have the task, when you have reams of existing, non-namespace qualified code, of a global edit (which really you must admit is not that difficult - I do it all the time. Maybe your editor is not up to scratch - Try Meditor Pete