|
> From: Wilbert van der Hoeven > > I would never set On to *Off. But I can't guarentee that the other 5 > programmers that changed the program after I wrote it will not have > changed the program and set On to *Off somewhere. Wilbert, I'm not going to argue this point. If you work in a shop where someone changes someone else's programs in this way, then you have serious problems. This is not a valid argument in any shop I work in. > I think that the DO statement is not the right place to leave the loop. > The right place for me to leave the loop is the place where you meet a > condition to leave that loop. No chance of making mistakes. That's your opinion, which I disagree with. In fact, most of the time I disagree with any sort of statement that says one syntactical construct is "better" than another; there are always reasons to use different techniques and in the end, it's all still Branch-On-Condition. But since we're discussing opinions and you're proposing an absolute, we should probably just leave it at that. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.