The "problem" with defaulting them to the enabled state is that the meaning of previously valid programs change. (Of course it is unlikely that someone happened to use a variable with an odd name like that -- some might say pathological.) We generally like changes to be backwards compatible. Having the default as disabled preserves backwards compatibility.
Ken On Mon, Aug 17, 2015 at 7:28 AM, andy pugh <bodge...@gmail.com> wrote: > > http://www.linuxcnc.org/docs/html/remap/structure.html#_optional_interpreter_features_ini_file_configuration_a_id_sub_ini_features_a > > The man-page says, quite correctly, that the option to read INI and > HAL values in G-code should not be documented in that manual section. > > A decision probably needs to be made about whether the feature is "in" > or "out", and if so the enabling flag should probably be defaulted in > the "on" direction and those sections moved to a more logical place. > > -- > atp > If you can't fix it, you don't own it. > http://www.ifixit.com/Manifesto > > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > -- Kenneth Lerman 55 Main Street Newtown, CT 06470 ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
