Re: Testing 2.3

new topic     » goto parent     » topic index » view thread      » older message » newer message

Robert Craig writes:
----------
> ïÔ: Robert Craig <rds at RapidEuphoria.com>
> ëÏÍÕ: EUforum <EUforum at topica.com>
> ôÅÍÁ: Re: Testing 2.3
> äÁÔÁ: Friday, December 07, 2001 00:21
>
> Igor Kachan writes:
> > I got too many Warnings to fit in one screen,
>
> Well if it's just a matter of too many warnings,
> rather than incorrect warnings or errors, then
> perhaps I can cut down on them.
> (You could also say "without warning")
>
> I assumed that the case of duplicate globals
> would be fairly rare, and people would want
> to be warned about it, but maybe I should take out that
> warning, since you'll get an error if you try
> to actually use one of the globals ambiguously
> without a namespace qualifier.

Sorry please, my first perplexity was :

> > I just have *copied* graphics.e into graf.e
> > and then ran the program:

> > -- test.ex
> > include graphics.e
> > include graf.e
> > -- end of program

> > Nothing happened ...

Why "Nothing happened ..." if two includes
are fully non-compatible ? - this is my question,
sorry please my English again.

The usual practice, I think, is testing
of includes as the first action in programming
of any new program.

And if interpreter will abort program on any
*first names conflict* then anyone can understand
immediately what actually happens.

Program can not run fine with names conflicts,
so abort it on the first one, then on the second
one and so on. There are tools for resolving any
conflicts in the bud - renameing and qualifiers.

Just some thoughts.

Regards,
Igor Kachan
kinz at peterlink.ru

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu