> It would be better if we didn't have to remember where there were
> underscores and where there were hyphens when typing HAL pin names.
> The simplest solution is to go to all-hyphens. However, the problem
> with that is that all existing configs out there would break.
> My suggestion is a half-way house to allow us to have a consistent pin
> naming scheme in future releases, without breaking working machines.
> There could even be a stated aim to remove the _/- equivalence at some
> future point once everything is converted.
>
How about this, (more detail of what you hinted);
send a message to users about what and why
In Master add your code to make _/- equivalent.
In Master immediately start to fix all components and sample configs.
send a warning to users about upcoming removal of equivalence code.
When when ready to create 2.6 remove the equivalence code.
take a little flack from all the users who ignored the warning :)
Chris M
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
