Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!imagen!auspyr!mick
From: mick@auspyr.UUCP (Michael J. Andrew)
Newsgroups: comp.lang.c
Subject: Re: gotos
Message-ID: <4160@auspyr.UUCP>
Date: 11 Apr 88 22:41:50 GMT
References: <2571@cognos.UUCP> <77200029@uiucdcsp> <1988Apr5.213343.1528@utzoo.uucp>
Reply-To: mick@auspyr.UUCP (Michael J. Andrew)
Organization: Austec Inc., San Jose, Ca, USA
Lines: 23

In article <1988Apr5.213343.1528@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>> Sometimes, gotos are perfectly justifiable because they vastly
>> simplify and clarify you code.
>
>And once in a long while, there is no better way.  A loooong while.
>If I were running a software house, I'd be tempted to say that using
>a goto -- except in fixing a program that already uses them -- means
>having $50 docked from your pay.  It's not *forbidden*, you understand,
>it's just that you have to want it really badly!

This is a excellent extension to a scheme I keep proposing half-
seriously to management, to encourage good programming
practices among novice, sloppy or lazy programmers.

Provide each member of the team a $500 bonus at the start of a new
project, but deduct $50 each time a global variable is introduced
into the design.

Wh
-- 
-------------------------------------------------------------------------
Michael Andrew		Sr. Systems Engineer	Austec, Inc.  San Jose CA.
mick@aussjo.UUCP				(408) 279 5533