[Home]Named O-Words

LinuxCNCKnowledgeBase | RecentChanges | PageIndex | Preferences | LinuxCNC.org

Difference (from prior major revision) (no other diffs)

Removed: 1d0


Changed: 3c2
(Note: named owords have not been implemented yet)
(Note: named owords have now been implemented in Trunk (2008-03-15))

Changed: 17c16
Local named owords are stored internally as the subroutine name, followed by an '_', followed by the local oword name. In the case of a local named oword that is not within a subroutine, the letters 'main_' are prepended to the name. The character '_' may be part of an o_word name, but may NOT be the first character.
Local named owords are stored internally as the subroutine name, followed by an '#', followed by the local oword name. In the case of a local named oword that is not within a subroutine, '#' is prepended to the name. The character '#' may NOT be part of an o_word name.

Named o-words for rs274ngc

(Note: named owords have now been implemented in Trunk (2008-03-15))

Named owords can have a similar syntax.

o<a label> is a named label. Named labels are of local scope with the exception of the named labels which refer to subroutines. Thus, two subroutines may have owords "o<Loop>" without causing an error.

 o<BoreHole> sub
 o<BoreHole> return
 o<BoreHole> end
 o<BoreHole> call

All refer to the same subroutine.

Local named owords are stored internally as the subroutine name, followed by an '#', followed by the local oword name. In the case of a local named oword that is not within a subroutine, '#' is prepended to the name. The character '#' may NOT be part of an o_word name.


LinuxCNCKnowledgeBase | RecentChanges | PageIndex | Preferences | LinuxCNC.org
This page is read-only. Follow the BasicSteps to edit pages. | View other revisions
Last edited March 15, 2008 6:09 am by KennethLerman (diff)
Search:
Published under a Creative Commons License