On 24.03.12 15:31, Michael Haberler wrote: > Am 24.03.2012 um 13:27 schrieb Erik Christiansen: > > On 23.03.12 11:20, Michael Haberler wrote: > >> You will find lots of examples for embedded Python usage in the canned > >> demos under configs/sim/remap, and regression tests using these > >> features, like under tests/remap and tests/interp. > > > > In > > manual-toolchange-with-tool-length-switch/nc_subroutines/manual_change.ngc > > > > I see "o<manual_change> sub". That's spiffy, but doesn't quite seem to > > be documented in either > > > > http://www.linuxcnc.org/docs/html/gcode_main.html > > Since technically this is just a plain O-word procedure (except for > the parameter passing method), there is no point documenting it in the > G-code reference.
What caught my eye there was the use of named subroutines. The doco page only allows us numbered subroutines, e.g. O100 . AH, The Penny Drops! The subroutine is alone in the file, and we can use named subroutines it they're in a file of that name. For a moment there, I thought that along with the new subroutine return values, there was also an extension of the "O100 call" to allow "O<subroutine_name> call" for routines defined in the calling file. Sorry for the confusion. Erik -- I frequently hear "it's not rocket science, is it?". No, but I recently saw a slide of the infamous "O rings" which failed on the Challenger shuttle. Under a layer of frost, you can just read "Do not use in temperatures below 16C". So even rocket science is not rocket science. - User feedback seen on BBC website ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users