OpenEuphoria

Re: Euphoria Standard Library on UBoard

• Posted by Gordon Webster <gwalias-bb at yahoo.com> Jul 28, 2005
• 564 views

Jason Gade wrote:
> 
> Bernie Ryan wrote:
> > 
> > Alexander Toresson wrote:
> > > 
> > > Juergen Luethje wrote:
> > > > 
> > > > Jason Gade wrote:
> > > > 
> > > > > Tommy Carlier wrote:
> > > > >
> > 
> > > Solution: create a mutex which is locked when enum() and the other
> > > functions in enum.e
> > 
> > You already have a conflict with your standard Library
> > if you enum() function because the global function exists
> > in my libraries. So you better come up with a different name.  
> > 
> > Bernie
> > 
> > My files in archive:
> > w32engin.ew mixedlib.e eu_engin.e win32eru.exw
> > 
> > Can be downloaded here:
> > <a
> > href="http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&amp;win=on&amp;lnx=on&amp;gen=on&amp;keywords=bernie+ryan">http://www.rapideuphoria.com/cgi-bin/asearch.exu?dos=on&win=on&lnx=on&gen=on&keywords=bernie+ryan</a>
> > 
> 
> Whew, I really wanted to flame on when I read this, but I collected my
> thoughts and
> will try to present them in a calm manner.
> 
> We are trying to come up with a so-called "standard" library.  Since there are
> so many
> libraries and files in the archives, naming conflicts are going to happen. How
> many
> times do 'TRUE', 'FALSE', and boolean() show up?
> 
> Maybe we'll call our function 'enumerate()' or
> 'next_in_a_list_of_unique_numbers()'
> or whatever. But if enum() is the best choice, then we will use it. It's
> certainly
> better than asdf()!
> 
> Users will face a choice: use our library and not yours (or vice-versa) or
> namespace
> one of the libraries.
> 
> Since the code in ESL will be public domain (or close to it) people could just
> cut-and-paste
> if the file that includes enum() causes conflict.
> 
> Whatever.  No one owns the names, though. And we're a long way off from being
> an official
> part of Euphoria.
> 
> =====================================
> Too many freaks, not enough circuses.
> 
> j.
> 

Absolutely!

Good grief ... If we start trying to avoid all the really obvious names 
for modules and routines that every other Euphoria coder has ever used in
their own stuff, we'd have something like ..

function enum_but_not_bernies_or_jims_enum_but_kinda_similar()

Is somebody else going to come forward and stake their claim to the 
exclusive use of the name 'string.e' for a module that contains
string-handling functions?

People please!

- Gordon