Hello Andy,

Wednesday, September 13, 2000, 12:00:20, you wrote:

>>   The argument about it being easier or more proper to maintain a
>>   program using one over the other is ludicrous at best.  Why is it
>>   easier to use a CALL for instance than a GOTO?  Or a GOSUB in place
>>   of a CALL?  This seems rather dumb to me.  Most of the programs I
>>   have written, regardless of language, I get to maintain.  No problem
>>   there right?

Because when a called sub or function gets to the end or return
statement it returns to the line after it was called. This can *not*
be guaranteed with GOTOs. Also how big are these programs. Most of us
programmers find it hard enough to go back to a 10000 line, well coded
and commented procedural program after a few months of not looking at
it. The other point is a professional programmer should always write
code as if they're going to be graded on it or someone else will have
to maintain the software. Then there is the team programming where
more that one programmer will be working on the project. How does your
sloppy, spaghetti logic code fit in then? When using small processors
such as pics with a shallow stack GOTOs are acceptable. In proper
systems they should never be used at all. VB programmers among you
will think of VBs terrible error handling. On Error Goto Errohandler.
Well done M$, perfect bit of thought.


--
From Jamie Dainton
Wednesday, September 13, 2000 13:42:21
The Bat! 1.46 Beta/5
Windows 98 4.10 2222

mailto:pgp@dainton.org.uk?subject=sendKey

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu