Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
One exit per procedure/function/codeblock to what purpos
Message
De
08/10/2003 07:50:17
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
 
À
08/10/2003 07:24:01
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00835552
Message ID:
00836136
Vues:
24
>SNIP
>>Peter,
>>Strongly agree. I too doesn't follow the 'one exit point' rule or even don't accept it as a rule but as pure preference.
>>From readability point I find it much easier to follow code that has 'early' returns :)
>
>Hi Cetin,
>
>I believe that a large part of the problem with this issue is that it used to be taught, in formal instruction, as a rule.
>Certainly in the days when GO TO was a common language command (i.e. COBOL, Basic) instructor would hammer home the "rule" but I believe it was mainly to get everyone to stop using GO TOs in their code. It seems people continued with the rule even after GO TO disappeared.
>
>cheers
>
>>Cetin

Hi Jim :)
Might be.
Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform