On May 24, 2013, at 03:43 , andy pugh wrote: > I don't see any reason for this to be a parameter. And I can think of > a use for it as a pin. (see users list, gantry thread) > > A parameter-to-pin switch should never break any configs, so I suggest > changing it to an output pin, and pushing that to the 2.5 branch. > > Any objections?
I object to changing it in 2.5, but i don't object to changing it in master (if you test it and make sure none of the sample configs break). We're way too deep into the 2.5 release to change stuff like this. Pins and parameters do behave differently, and while we may not have any configs that care, we don't know what our users are doing. I can imagine (for example) setups that use scripts to look at 'halcmd show', that would get confused if axis.N.home-state moved from the Parameters list to the Pins list, so these hypothetical users would be affected by the change. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
