Re: Re: G-code user variables; convention?

Brian P wrote:

>if the interpreter speed is a major issue COMPILE the G-code :-)
>yes we do have a machine in the shop that runs compiled 274 programs

Brian,

Yes, I too have played with 'compiled gcode'. My point is that we're
absorbing the increased processor speed available by not prioritising
well, IMO. Write a fast interpreter (using methods of the past, when
they HAD to be used) and you won't HAVE TO compile your gcode!! The
increased processor speed (over the past) is USED to RUN the code,
since we SAVED it by writing tight interpreter code.

Another note along this line of thinking came up awhile back. EMC has
a standalone interpreter with LOTS of error checking. Then the error-
checked code is run through the SAME error checks again at run time!
I mentioned 'cleaning out' the run-time interpreter, so the speed
gained could be used for trajectory planning,etc. RayH thought it
seemed a good idea, and asked me to work on it. I told him my plate
was already full. Don't know from there what happened/is happening?

Hope this helps.

Ballendo