Clarify o-code numbering and scoping rules in docs#3891
Merged
andypugh merged 1 commit intoLinuxCNC:masterfrom Mar 31, 2026
Merged
Clarify o-code numbering and scoping rules in docs#3891andypugh merged 1 commit intoLinuxCNC:masterfrom
andypugh merged 1 commit intoLinuxCNC:masterfrom
Conversation
Document that control flow o-words (if/while/do/repeat) are locally scoped to their subroutine and can be safely reused across different subroutines, while subroutine definitions are global and must be unique. Add example showing valid reuse of o-numbers across subs. Ref: LinuxCNC#3880
grandixximo
force-pushed
the
issue-3880-fix
branch
from
f2eb7da to
f5829c1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document that control flow o-words (if/while/do/repeat) are locally scoped to their subroutine and can be safely reused across different subroutines, while subroutine definitions are global and must be unique. Add example showing valid reuse of o-numbers across subs.
Ref: #3880
I think after this the issue can be closed, the docs are much clearer, the issue was more about docs than anything, but proper errors also help.