🚀 go-pugleaf

In <15...@shlump.nac.dec.com> pi...@huron.enet.dec.com (Garison Ellsworth Piatt) writes:
>
>In article <1172@meaddata.mead.UUCP>, gordon@mead.UUCP (Gordon Edwards) writes...
>*In light of the stupid user discussion, how about a discussion of stupid and
>*embarrassing programming errors.
>
>Though I've had my share of stupid mistakes (and may post some of them),
>I think this one, made by an associate of mine, tops anything anyone can
>do.
>
>This acquaintance (who, for the sake of his career, will go nameless) and I
>are working on a joint project for the IBM PC.  I'm working on the internals
>and he is writing the user interface for one of the utilities.  Luckily, this
>utility will be the only thing resident in memory when it runs, for it is
>written as follows:
>
>	main()
>	{
>	    /* Some general initialization code */
>	    main_1();
>	}
>
>	main_1()
>	{
>	    /* Some menu initialization code */
>	    begin_1();
>	}
>
>	begin_1()
>	{
>	    /* Code to display the menus */
>	    main_1();
>	}
>
>
>... and so on.  He uses this perverse style everywhere he needs to loop
>between two functions.  I tried to make this thing crash one day, but with
>only four bytes stored on the stack per function call, it takes a long time
>to fill up 640K.  I got bored before it had a chance to crash.   I tried
>to get him to change this, but he said that as long as it runs alone, nothing
>will happen.
>
>Oh, well.

OH, WELL (??!?) He says?
This "associate" of yours, is he typical of the people that you hang out
with?  If so, it explains a lot.  I sure care a lot more about programs
that I am working on than to let some other programmer f**k up like
this.

As Clay is so fond of saying.....

idjit.
-- 
G. Wolfe Woodbury @ The Wolves Den UNIX, Durham NC
UUCP: ...dukcds!wolves!wolfe   ...mcnc!wolves!wolfe         [use the maps!]
Domain: wolfe%...@mcnc.mcnc.org    wolfe%...@cs.duke.edu
[The line eater is a boojum snark! ]           <standard disclaimers apply>