<somebody> wrote: > > > > > Changing all "_" to "-" will break all the existing configs (not only > > the sample configs, which can be changed by a script). > > However, I might have a solution: > > > > I can't think of any situations where swapping - for _ leads to > > ambiguity, so why don't we just make HAL not care about the > > difference? Then we can change everything to suit the canonical > > definition, but existing configs with _ in pin names will still work. > > Then we can _know_ that it is always "-" without having to look at the > > docs (and if we are wrong, or use _ instead, it doesn't matter). This breaks there being an exact match between what is specified and what hal pins are connected. While it solves one problem, it could lead to all sorts of really ODD problems down the road, when some files have "_" and some use "-" interchangeably. For instance, parameters are pulled by name from the ini file and used to set hal parameters. Maybe there would be no confusion there, either.
Jon ------------------------------------------------------------------------------ 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
