• Subject: RE: Max. program size (and goto)
  • From: Rob Berendt <rob@xxxxxxxxx>
  • Date: Mon, 22 Mar 1999 13:18:30 -0500

Or the new 'GOTO' statement:
'A'   CABEQ  'A'     END
I've seen this BS in some packages.






JFritz@sharperimage.com on 03/22/99 01:08:20 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        RE: Max. program size (and goto)

In the best of all possible worlds, the chain of ENDIFs below would result
from a series of comparisons that really did depend on one another and all
needed to be executed. Otherwise there's usually a way to avoid them without
using a GOTO.  If you're maintaining someone else's code, it's usually too
much risk/trouble to simplify the logic, though.  

> -----Original Message-----
> From: Ken Slaugh [mailto:ken.slaugh@cm-inc.com]
> Sent: Sunday, March 21, 1999 1:43 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: Max. program size
> 
> 
> That depends on what you think 'bad programming technique' is. I would
> rather see a GOTO END statement then:
> ENDIF
> ENDIF
> ENDIF
> ENDIF
> ENDDO
> 
> 
> Ken Slaugh
> Senior Programmer/System Analyst
> AS/400 Professional Network Administrator/MSE
> Specialist - Client Access/400
> Chouinard & Myhre, Inc.
> 
> > -----Original Message-----
> > From:       Balaji Venkataraman/commsoft 
> [SMTP:bvenkata@commsoft.net]
> > Sent:       Friday, March 19, 1999 11:30 AM
> > To: MIDRANGE-L@midrange.com
> > Subject:    Re: Max. program size
> > 
> > GOTO will not affect the pgm size a great deal.  It is just a bad 
> > programming technique.
> > 
> > Balaji
> > bvenkata@commsoft.net
> > 
> > 
> > 
> > 
> > "Rajeev Asthana" <Rajeev_Asthana@paramount.com> on 03/19/99 01:14:24
> > PM
> > Please respond to MIDRANGE-L@midrange.com
> > To:     MIDRANGE-L@midrange.com
> > cc: 
> > Subject:        Re: Max. program size
> > 
> > How come GOTO is going to affect program size?
> > 
> > 
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to 
> MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to 
> MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to 
> > MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator: 
> > david@midrange.com
> > +---
> > 
> > 
> > 
> > 
> > 
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to 
> MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to 
> MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> > david@midrange.com
> > +---
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to 
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: 
> david@midrange.com
> +---
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].