archivist noticed that the log file was updated prior to being ran. The following example shows this.
; open test.txt in Gedit and remove any logs and save
; start the program then click on Gedit then click on update before the sub is called
; the file is updated before the first move
o100 sub
(LOGOPEN,test.txt)
G0 X0
(LOG,X#5420)
G0 X1
(LOG,X#5420)
G0 X2
(LOG,X#5420)
(LOGCLOSE)
o100 endsub
G4P10
o100 call
M2
The problem happens on 2.6 too.
<archivist> it is running on an older version 2.5.4</archivist>
I think this observed behavior has to do with the fact that the logged quantities are knowable during interp time, since there are no queue busters involved. Adding a G38.3 to the sub causes the logging to stop until run time (ie until after the g4 finishes).