Re: From a newbie
>Euphoria 2 will short-circuit, and give a warning message with those
>programs where it could led to a problem, when the programmer is not
>consider the short-circuiting..
Will do or does?
>>Euphoria language extension suggestions:
>>
>>1. If answer for Q2 is "No" make it possible - in/out arguments.
>>in - argument is an input (default)
>>out - argument is an output
>>in out - both as input and output
>I disagree, the programmer using the function wouldnt preciously know =
which
>variables could or could not have been altered.
Yes, the programmer knows it - right from the function interface he/she =
declares (using in/out).
>However, a very nice replacement trick for this is: (something I would =
like
>to see added)
>{ name, addres, phone } =3D lookup_db (name)
Oh, great! It looks like unification (what about anonymous variables?).
>>2. Structured gotos (as in Java) and exceptions implementation.
>I find them a bit scary.. but there are cases they are handy..
>What about this one, Robert ?
>exit (3) -- jump out three levels
Now, I disagree. It's only partial solution - I don't know in advance if =
I put the code with exit(3) inside/outside another block (so the level I =
want to jump out could be changing). The labeled (i.e. named) statement, =
which is to be jumped out to, is much more robust and clear.
Tom
|
Not Categorized, Please Help
|
|
