OpenEuphoria

Re: Wishlist

• Posted by daryl_vdb at HOTMAIL.COM Jun 27, 2001
• 547 views

>On Wednesday 27 June 2001 00:49, daryl_vdb at HOTMAIL.COM wrote:
>
> > >Disadvantages:
> > >     None - won't break any existing code.
> >
> > except if the existing code has a variable, constant, function or 
>procedure
> > named "version" or "requires".
>
>True enough - but the same thing could be said of *any* new keyword.
>Maybe I would like to create a variable named "cursor" in my program.
>I can't, it's already taken. Same with 'value', 'where', etc.
>
>If we don't want any new keywords, then Rob can stop work on 2.3,
>and save himself a lot of trouble, because there's not much he can
>add.
>
>Of course, proper namespacing could make that a moot point, as these
>two words could exist outside of user namespace.
>
>Regards,
>Irv

I agree - new keywords must be created for namespaces.  It would, however, 
be nice if Euphoria could remain backwards-compatible. IOW, if it encounters 
a symbol defined with the same name as a keyword, assume the program was 
made for an earlier version of euphoria and allow it.  And give a warning, 
of course.