1. Re: Modified Include System
- Posted by Vincent <darkvincentdude at yahoo.com> Feb 08, 2006
- 429 views
- Last edited Feb 09, 2006
Jason Gade wrote: > > Vincent wrote: > > > > Jason Gade wrote: > > > > > I suggest that anyone who writes a file that is intended to be included > > > use > > > namespaces for files that *it* includes. Then it exports any functionality > > > with > > > it's own global routines if it needs to do that. > > > > > > Programmers cannot rely on moving a symbol over two levels of include > > > files > > > without the possibility of a namespace clash. Therefore this is the best > > > workaround > > > for something that is unlikely to be changed. > > > > > > Yes, it means that older or unmaintained libraries will have to be changed > > > if > > > someone runs into a naming conflict. > > > > > > > That doesn't solve the problem with files with the same name. Using > > namespaces > > does not bypass the issue. Maybe you're talking about a whole different > > problem? > > > > > j. > > > > > > Regards, > > Vincent > > Right. I'm thinking of two different problems. Sorry. > > With the include naming issue, you'll just have to rename a file. Sucks, > but... > > The issue I'm mainly concerned about is covered here: > <a > href="http://www.listfilter.com/cgi-bin/esearch.exu?thread=1&fromMonth=6&fromYear=8&toMonth=8&toYear=8&keywords=%22another+look+at+namespaces%22">http://www.listfilter.com/cgi-bin/esearch.exu?thread=1&fromMonth=6&fromYear=8&toMonth=8&toYear=8&keywords=%22another+look+at+namespaces%22</a> > > I think the problems are related, that's why I've been discussing it. > > -- > "Any programming problem can be solved by adding a level of indirection." > --anonymous > "Any performance problem can be solved by removing a level of indirection." > --M. Haertel > j. Oh yes that problem... you will notice that I've fixed that in my custom interpreter; however the code I used wasnt written by me. I suspect Matt will eventually implement in OOEU too, since he did it with his modified Euphoria v2.4 interpreter. Robert has dishonored his promise to implement that in v2.5 and instead decided to put it on the "back burner". However I think the PD-source made up for his broken promises. Regards, Vincent