Thought you guys/gals might find this of interest in light of the conversation
thread here.
The engineering program at Queen's University (Canada) gives a 0% grade on
assignments from students that use a GOTO in their code. LOL.
http://www.ece.queensu.ca/hpages/courses/elec290/qbot/programs.html
3 GOTO's and Program Flow Although GOTO's are provided in PBASIC, their use
can make for spaghetti code that no Queen's engineer should be caught dead
producing. You should absolutely avoid the use of the GOTO completely! NOTE:
Use of GOTO's for any purpose will result in a mark of ZERO being assigned for
that program.
Derek
Tom Keene <[EMAIL PROTECTED]> wrote:
Actually, the use of a runtime error exception block requires the use
of at least one Goto. RB hides the statement from the programmer,
but it's there.
>
> Message: 1
> Subject: Re: Goto and Gosub process not intuitive or is it just not
> there
> From: Arnaud Nicolet
> Date: Sun, 13 Aug 2006 03:44:36 +0200
>
>
> Le 13 ao=FBt 06 =E0 03:30 Matin, Russ Jones a =E9crit:
>
>>
>> On Aug 12, 2006, at 9:06 PM, Arnaud Nicolet wrote:
>>
>>>
>>> Le 8 ao=FBt 06 =E0 06:31 Matin, Norman Palardy a =E9crit:
>>>
>>>> GOTO is mostly never required and should be avoided in 99.9% of =20
>>>> all cases where you think you need it.
>>>
>>> Hi,
>>>
>>> why should it be avoided?=20
>>> _______________________________________________
>>
>> Early in the development of "structured programming" - which is =20
>> only a part of the Object-oriented environment we now enjoy,
>> people =20=
>
>> tried to argue that GOTO was harmful, and violated the structure =20
>> "rules" - and prevented proving programs correct. This was =20
>> primarily in response to the "spaghetti code" - tangled logic and =20
>> messy code - that people were then using to make buggy programs.
>>
>> Unfortunately for those who argued against the "goto", it was easy
>> =20
>> to develop correctness rules for it, and most of the other =20
>> arguments fell by the wayside. Except the fact remains that those =20
>> who develop tangled code without clear paths of control still make
>> =20
>> many program "bugs" that are very difficult to find.
>>
>> SO - the reason to avoid GOTO today is that it is dangerous. It's =20
>> too easy to make a mess if you use a GOTO. And maintenance =20
>> programmers may be totally unable to help you resolve your
>> problems =20=
>
>> if you do. But it works, and, under very special circumstances,
>> its =20=
>
>> use may be justified. You need to learn a lot about programming =20
>> before you can make that argument stick, though.
>>
>> For now, let's just say that you don't need it, and it's too =20
>> dangerous.
>
> Thanks.
> (anyway, I'm not a newbie programmer and like gotos) like that:
_______________________________________________
Unsubscribe or switch delivery mode:
Search the archives of this list here:
---------------------------------
Get your email and more, right on the new Yahoo.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
