>>40
To put it simple, if you are on a level that could be considered advanced, and you cannot cope, handle, define, implement or at least understand why goto is present, especially if you are trained in computer algorithms and/or architectures, and the real-world arguments presented are brushed away with a tone equal to "you can program everything with just a for(;;) loop, so ban do{}while() and while(){}, then..., well..., I guess you are forcibly narrow-minding yourself to a degree considered ignorance is bliss.
There are levels where the usage of goto are preferred and which can be argued. But to kill this language construct just because it is not applicable in your field, or to ban lecturing of it because you see no sense or practical usage for it, and using arguments that reflect insufficient knowledge of truly advanced computer science is more like wasteful language purism.
Some people just need to set the standard. I'm fine with that, but please don't restrict or ridicule the advanced levels.