> If you're going to completely ignore my problem and rant about goto statements,
> at least tell me WHY they're bad.
There is a somewhat drawn out discussion about the use and abuse of
(with participants arguing on both sides) starting here:
> I mean, seriously, if everybody keeps telling you that goto's are bad,
> at what point do you start to think that, maybe, they might be bad?
At the point when you have reasoned it out for yourself and reached a cogent conclusion. When you do not just 'think' that excessive use of
is bad, but you know why it is bad. Not till then. When you would be able to say something more than: "goto's are terrible, and getting used to them is a truly terrible idea if you ever want to be more than a terrible programmer you should make the effort to stop using them". When you can say why unbridled use of
Hint: A whole lot of people swear that the use of
anywhere is bad. The C++ community as a whole had three opportunities to say: "we know that the use
anywhere is unconditionally bad; we keep it only for compatibility with legacy code. It is deprecated" - once in 1998, again in 2003, and recently in 2013; but it did not. Clearly there is more to it than blind unquestioning belief; there is something worth thinking about.
You don't become a good programmer by subscribing to religious beliefs; you become one by learning to think for yourselves.