From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3EB90CC5.7010703@ameritech.net>
From: northern snowfall <dbailey27@ameritech.net>
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.4.1) Gecko/20020518 Netscape6/6.2.3
MIME-Version: 1.0
To: 9fans@cse.psu.edu
Subject: Re: [9fans] same functions everywhere
References: <20030501160047.7231.qmail@g.bio.cse.psu.edu> <000c01c3147c$c7665ae0$7b83773e@SOMA> <3EB8E817.4090609@ameritech.net> <20030507124006.D26796@cackle.proxima.alt.za> <3EB9049D.50500@ameritech.net> <01f601c31494$ebe8e550$644cb2cc@kds>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed,  7 May 2003 08:40:21 -0500
Topicbox-Message-UUID: a1736674-eacb-11e9-9e20-41e7f4b1d025

>
>
>Okay, that seems *really* silly to me!
>
hehe
Well, the reason why I make it a seperate
function is because:
    1) unless specified otherwise we have to
        assume that the function will be used
        multiple times.
    2) if used multiple times we're actually
        minimizing instructures in the code
        segment by using a seperate function
    3) modular reusable code is easy to read,
        use, audit, test, retest, hack, recode, etc
    4) Because I rule
But, sure, your way works well, too :)
You're right about goto, too. Lots of people
are afraid of goto, but, as long as its used
wisely, it ain't nothin' but a jump. It all
breaks down to the right choice for the
given situation.
Don