1. namespace qualifiers

I think this shouldn't be allowed :

include <library> as <keyword> | <builtin>

Example :

    include get.e as puts
    puts(1, "Hello !") -- puts has not been declared

Instead of that, interpreter should say
    include <library> as <builtin>
Attempt to redefine <builtin>

btw. if you want to see full list of changes in Eu 2.3,
run on Linux
   diff -r -u euphoria22 euphoria | more 

You'll see interesting things, eg.
Bill Clinton replaced by George Bush in email.exw smile

Regards,
      Martin Stachon

martin.stachon at worldonline.cz
http://www.webpark.cz/stachon

new topic     » topic index » view message » categorize

2. Re: namespace qualifiers

Martin Stachon writes:
> I think this shouldn't be allowed :
>
> include <library> as <keyword> | <builtin>

It prevents you from using a keyword 
(like "while", "procedure", etc.)
as your namespace id, but it allows you to
override a builtin routine, just as you can already
when you define a new routine. 
It seems consistent to me.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view message » categorize

3. Re: namespace qualifiers

Rob wrote:
> Martin Stachon writes:
> > I think this shouldn't be allowed :
> >
> > include <library> as <keyword> | <builtin>
> 
> It prevents you from using a keyword 
> (like "while", "procedure", etc.)
> as your namespace id, but it allows you to
> override a builtin routine, just as you can already
> when you define a new routine. 
> It seems consistent to me.

But this :

    include get.e as atom

gives you an error, because namespace qualifier "atom"
overrides builtin type "atom" in get.e, which shouldn't happen -
refman says :
    "A namespace identifier has local scope.
    It is known only within the file that declares it,
     i.e. the file that contains the include statement"

Interpreter should also say that builtin is redefined by qualifier,
like if it is redefined by procedure.

[other issue]

I think it may be written in relnotes that exw now in 2.3
waits for a key to be pressed after a console program exits.
In lots of programs the line

    if getc(0) then end if

before exit is now no longer needed. 
(Including dsearch.exw)

Regards,
    Martin Stachon

new topic     » goto parent     » topic index » view message » categorize

4. Re: namespace qualifiers

Martin Stachon writes:
>  include get.e as atom
>
> gives you an error, because namespace qualifier "atom"
> overrides builtin type "atom" in get.e, which shouldn't happen -

Ok, thanks. I'll reconsider this issue.

> [other issue]
> I think it may be written in relnotes that exw now in 2.3
> waits for a key to be pressed after a console program exits.
> In lots of programs the line
>
>    if getc(0) then end if
>
> before exit is now no longer needed. 

exw for 2.3 alpha sometimes needs you to hit Enter twice
when exiting a console window. That's a bug. I've fixed it now. 
Tone Skoda reported it also.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view message » categorize

5. Re: namespace qualifiers

Rob Craig writes:

> exw for 2.3 alpha sometimes needs you to hit Enter twice
> when exiting a console window. That's a bug. I've fixed it now. 
> Tone Skoda reported it also.

ecw is also affected.

    Martin

new topic     » goto parent     » topic index » view message » categorize

6. Re: namespace qualifiers

Martin Stachon writes:
> ecw is also affected.

Yes. All the Windows-related programs go through
the same termination code, and sometimes you need
to hit Enter an extra time. It's fixed now. Thanks.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com

new topic     » goto parent     » topic index » view message » categorize

Search



Quick Links

User menu

Not signed in.

Misc Menu