Currently, labels in the human-readable bytecode are not localized but global.
If you have two procedure implementations and both have a label called .exit then the assembler will error out that it's a redefinition. Here's a code example of what I mean:
This shouldn't happen because jump labels are entirely local and, given that there's no access to the instruction pointer register, there's no way that a direct jump from one function to another's code space can occur anyway.
Currently, labels in the human-readable bytecode are not localized but global.
If you have two procedure implementations and both have a label called
.exit
then the assembler will error out that it's a redefinition. Here's a code example of what I mean:This shouldn't happen because jump labels are entirely local and, given that there's no access to the instruction pointer register, there's no way that a direct jump from one function to another's code space can occur anyway.