Long ago, no error message was generated for a break outside of any loop. I never used that behavior myself... I think I encountered it exactly once myself (in a situation where return was appropriate instead in that one case.)
I have read about it a very small number of times, and my memory is telling me that in the very small number of cases I saw, that the break could be commented out, as the logic was broken in the routines anyhow and failing to change flow of control did not make a substantial difference. Things like reading from the wrong directory, code that never worked properly, so commenting out the break just removed the syntax distraction to allow people to run the code and experience for themselves that the routine was rot.
Best Answer