On 2 March 2011 15:05, Michael Haberler <[email protected]> wrote: > 3. provide a, say, M-code to save the current active G/M-codes, feeds and > speeds in the interpreter stack frame, and either restore on return from > subroutine, or explicitely restore with another, say, M-code.
I like this approach. From the perspective of a computer programmer you expect subroutines not to mess with the calling program state. But as a CNC machinist you are likely to assume quite the opposite behaviour. So, I think making state-caching a deliberate action for programmers to do, and leaving CNC operatives with the behaviour they are used to is best. One hugely important application for this would be your toolchange-as-G-code stuff. It would be disastrous to perform a metric toolchange in inches! -- atp "Torque wrenches are for the obedience of fools and the guidance of wise men" ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
