On 23 September 2011 18:15, Jon Elson <el...@pico-systems.com> wrote:

>> > 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?

> 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.

The INI file _only_ uses CAPS and _ as far as I know, so that is consistent.

HAL isn't consistent, not even the page that defines a consistent
approach is consistent:
The canonical pin naming convention (
http://www.linuxcnc.org/docview/devel/html/hal/general_ref.html ) says
that all underscores have been removed,  then it defines a number of
parameters with underscores.

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.

-- 
atp
"Torque wrenches are for the obedience of fools and the guidance of wise men"

------------------------------------------------------------------------------
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

Reply via email to