I've threatened to do this, and since it is slowly moving towards master, I
thought I'd reduce the surprise factor by laying out plan and status:
The rundown of what it aims to fix:
• GUI's will be able to highlight source location wherever it comes from:
main.ngc, an oword subroutine, Python code, MDI strings ..
• run-from-line should become more bullet-proof.
• run-from-line will work on arbitrary conditions, not just line numbers; from
locations in subroutines, or depending on variables.
• a new 'Run up to here and pause' GUI option similar to RFL should be easy to
add.
• a call stack display should be easy to do
• the Interpreter's handling of O-words can be firmed up substantially, the
following statements should cause an error message during parsing:
• a 'return' or 'endsub' not within a sub defintion
• a label on 'repeat' which is defined elsewhere
• a label on 'while' which is defińed elsewhere and not referring to a
'do'
• a label on 'if' defined elsewhere
• a undefined label on 'else' or 'elseif'
• a label on 'else', 'elseif' or 'endif' not pointing to a matching 'if'
• a label on 'break' or 'continue' which does not point to a matching
'while' or 'do'
• a label on 'endrepeat' or 'endwhile' no referring to a corresponding
'while' or 'repeat'
The gory details: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?SourceContext
This *will* eventually affect code I dont know very well, mainly the GUI's
(note 'affect' != 'break without further changes', or so I hope).
I'd appreciate feedback on this.
- Michael
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers