Re: EOF and GOTO and 0th array element
jbrown105 <jbrown105 at speedymail.org> wrote:
> On 0, Juergen Luethje <jluethje at gmx.de> wrote:
> <big snip>
>>> Such as I. With goto, exit/continue/exit(n)/next(n) would not be
>>> needed.
>>> Of course, with goto, for..end for/while..end while/if..end
>>> if/select..end select or even procedure..end procedure/function..end
>>> function wouldn't be needed either.
>>
>> Right, but there has been good reasons why Rob nevertheless decided to
>> implement while..end while etc. in Euphoria.
>> Arguing this way, I also could say Euphoria would not be needed at all,
>> because programs can be written in assembler.
> Sorry, I meant to add that goto is a bad idea for replacing
> for/while/if/select
> (select is something else the language could use!)/procedure/function.
> goto does have its uses, but I agree that totally uncontrolled gotos
> can destroy the readability of the code.
Thanks, now I understand what you meant.
<snip>
>>> I think that all features should be implemeted,
>>
>> I disagree. Anything that is not necessary one the one hand, and has
>> the potential to cause harm one the other hand, should *not* be
>> implemented.
>
> As of version Eu 2.3, goto or some alternative is necessary.
As I'm rather new to Euphoria, could you please tell me what new
features of version 2.3 made goto or some alternative necessary
in your opinion?
> And while goto can create spagetti coding (I op for restricting use to
> routines if this is too big a problem, and this reduces the spagetti
> to procedures and functions only), I doubt very few people on this
> list would use it to do more than jump out of loops or to replace
> recursive routine calls.
>>> and that the programmer
>>> should choose one's own style from there. (Of course Rob would never
>>> agree to that, and I am better at Euphoria than I am with C, so I continue
>>> to write preproc to get around this limitation.
>>
>> Well, if you consider the lack of GOTO as a limitation, I can understand
>> you, of course. For me this is not a limitation. I've been programming
>> in PowerBASIC for about 10 years, there is GOTO of course.
>> I simply never needed it. 
> I've needed it only on a few occasions, for jumping out of multiple
> loops easily, and for speeding up recursive functions (in C mind you,
> I've had to do without in Euphoria). But it is those few occasions
> where it does provide usefulness. I'm not trying to completely
> advocate goto, but mere propose it as an alternative.
I think I understand your point of view.
About my point of view, I already wrote anything in my previous post,
I can't say something additional at the moment.
<just snipped the old stuff>
> jbrown
Best regards,
Juergen
|
Not Categorized, Please Help
|
|
