Mike Copeland wrote in a message to David Chord:
 DC> The help isn't to clear to me at the moment. Break I know and have
 DC> used before (nice quick and easy way to exit a loop :-), but continue
 DC> I'm not to clear on - does it mean that if you've used BREAK
 DC> somewhere, and a short time later want to jump back into that part of
 DC> the program, you just run CONTINUE and it jumps to the 'line' of the
 DC> program just after the break? 
 MC>    Excellent reasons _not_ to use Break and Continue!  
I didn't know about continue, but can already understand how to use it now, 
since it is simillar to something I learnt back in my early days of 
programming.
However, where is the problem with break, and how can you do a better or as 
good as job without using it?
It's all very nice to teach someone that something is the ultimate evil, but 
it does not make you a good teacher. In fact, if you don't try to show them 
an alternative method or even give them clues and let them learn by 
experience, you are virtually useless as a teacher, at least in that regard.
Note that I do appreciate your efforts and what you have taught me or made 
available to me and others over the last 5 years or so. But it does annoy me 
a lot when someone with more experience says 'You can't do that, it's the 
wrong way to do it and you'll have serious problems!' then walks off without 
offering a hint of a better/correct way of doing it.
Dave
Save your BBS! Join INTBBS_WK now! 
--- timEd 1.10
---------------