rE: Language Design

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

In my idEu project, I stopped coding while debugging the implementation of=
 goto.
Quite a hell really. Since I now contribute at an unexpectedly high level t=
o
the OpenEuphoria
project, this code is just sitting on the HD, waiting either for OE or EU w=
ith
useful features
to start flying.
	goto is not improper by itself, since all asm code use it without any othe=
r
alternative left. But it is probably too tricky to implement and leads too
easily to unmanageable/unmaintainable code, compared with its usefulness.
	I just object to having to understand gotoed code, and I'm free to refrain=

from using the statement. Controlled gotoes (generalized exit/next/retry/..=
.
to start/end of control blocks) seem to be much more useful, easy to
understand and safe to implement. Just a coder's opinion.

CChris


> Subject: RE: Language Design posted by: Brian Broker <bkb at cnw.com> Der=
ek Parnell in response to:
>
>>> Kat wrote:
>>
>>>> >
>>>> > On 28 May 2004, at 1:53, Ricardo Forno wrote:
>>>> >
>>>
>>>>> > > I agree wholeheartedly.
>>>
>>>> >
>>>> > So is that TWO votes in favor of "goto" in Eu ?
>>>> >
>>
>>> Well...I won't actually object to it being included, but just
>>> don't expect me to ever use it, or to trust a program that
>>> does use it
>>>
>>> --
>>> Derek Parnell
>>> Melbourne, Australia
>>>
>
> Nor would I choose to help to debug such a program...
> -- Brian
> (just my 1=A2)

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

Search



Quick Links

User menu

Not signed in.

Misc Menu