Using numbers for labels is certainly a good way to discourage goto's. Eliminating GOTO sure makes code a lot more readable and maintainable.
Assembler toolkit has a set of structured programming macro's that greatly reduces the need for branch labels. I hated macro's that required branch labels (e.g. EOF). Structured macros greatly improve maintainability. Macros only have goto logic so we are out of luck there. Sadly, in a product dev environment, every line changed was considered a risk and must be thoroughly tested. Most vendors won't allow developer's to make such massive changes unless there is a real business need. Regards, Jon. Bernd Oppolozer wrote: he was not courageous enough to leave goto and labels out of the language. So he came to this decision, to allow numbers as labels only, and to force them to be declared before using them. So: if you forbid branches aka gotos, you don't need alphanumeric labels; you don't need labels at all.
