> From: [email protected]
> Date: Mon, 2 Dec 2013 17:15:30 +0100
> To: [email protected]
> Subject: Re: [Emc-users] INI Tricks
>
>
> Am 02.12.2013 um 15:42 schrieb andy pugh <[email protected]>:
>
> > On 2 December 2013 13:23, Charles Steinkuehler <[email protected]>
> > wrote:
> >
> >> Perhaps with the hacking taking place on motion and the path planner and
> >> whatnot, these can migrate to HAL where it seems like they belong.
> >
> > Doing that will break every single existing configuration. (Unless the
> > new HAL pins take the rather unusual step of initialising themselves
> > from the INI file, if the entry exists)
>
We should not be afraid to break things (if it makes sense) on major versions.
Since we will break things anyways if we add ja4 that is the time to break
everything
else.
I now am wishing we had released 2.6 as it is and worked hard on 2.7 that will
break
everything.
2.6 is going to take forever to be ready and it's over due now.
Since it seems quite a few people are using 2.6 now we will be breaking their
configs
anways. (I realize that they knew that could happen, but if you wait so long to
release
features that are wanted/needed then we are part to blame)
> yes, but automatic migration is possible:
>
> parse the config values out of the ini file, create a .hal fragment using
> these values to init pin values, and add that to HALFILES=.. after the .hal
> file which loads motmod
>
I think we need to plan for changes that will break things occasionally rather
then
kludge two ways to do things.
Chris M
Chris M
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
