OpenEuphoria

Re: Euphoria Standard Library on UBoard

• Posted by D. Newhall <derek_newhall at yahoo.com> Jul 29, 2005
• 565 views

Vincent wrote:
> 
> Matt Lewis wrote:
> > 
> > > > snipped
> > 
> > This mostly works.  Where it won't is if two multi-file libraries have 
> > conflicting symbols, and don't use namespaces internally, or if you have 
> > more complicated library dependencies that haven't used namespaces for
> > everything.  This is the situation the the proposed namespace change would 
> > have fixed, but didn't make it into 2.5.  For those who don't recall or 
> > weren't around at the time, see this thread:
> > 
> > <a
> > href="http://www.listfilter.com/cgi-bin/esearch.exu?thread=1&amp;fromMonth=6&amp;fromYear=8&amp;toMonth=8&amp;toYear=8&amp;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>
> > ..and this:
> > <a
> > href="http://www.listfilter.com/cgi-bin/esearch.exu?fromMonth=5&amp;fromYear=9&amp;toMonth=7&amp;toYear=9&amp;postedBy=robert+craig&amp;keywords=Namespaces">http://www.listfilter.com/cgi-bin/esearch.exu?fromMonth=5&fromYear=9&toMonth=7&toYear=9&postedBy=robert+craig&keywords=Namespaces</a>
> > 
> > ...or my modified interpreter:
> > <a
> > href="http://www.rapideuphoria.com/exm.zip">http://www.rapideuphoria.com/exm.zip</a>
> > 
> > Matt Lewis
> > 
> 
> This namespace problem is solved in my modified interpreter as well. What
> excuse does
> Rob have? I'd also like to suggest AGAIN that included files with identical
> names but
> "different" file paths, should NOT be treated the same. Fixing that would
> require only
> a small change in scanner.e to compare full file paths internally, not just
> relative
> file names.
> 
> Regards,
> Vincent
> 
Yes, this is probably the single most limiting feature of Euphoria (although Kat
swould say lack of GOTOs). It is fundamentally absurd to think that "include
file.e" and "include my_includes/file.e" are the same! What if you have 2
versions of a library and your current program uses its parsing functions, now in
the new version of the library the parsing functions are changed and made
incompatible with your program but you want the new GUI it gives you, what do you
do? You'd have to copy all the files over and figure out which files include
which other ones only to discover that they both use different versions of a file
that does file handling. You would be in a world of programming pain that could
result in you having to practically rewrite entire files of someone elses code
which could be completely avoided by treating files in different folders like
they are, which is as completely different files. Now if there was a solid reason
why this shouldn't be done I'd be OK with that but so far I don't think I've seen
a single program or library that relies on this behavior and it can be easily
fixed (in fact it's already been fixed in other peoples code).

The Euphoria Standard Library project :
    http://esl.sourceforge.net/
The Euphoria Standard Library mailing list :
    https://lists.sourceforge.net/lists/listinfo/esl-discussion