On Sep 26, 2011, at 14:23 , Kent A. Reed wrote:
> On 9/26/2011 10:46 AM, SourceForge.net wrote:
>> Bugs item #3414029, was opened at 2011-09-26 07:43
>> Message generated for change (Comment added) made by seb_kuzminsky
>>> Comment By: Sebastian Kuzminsky (seb_kuzminsky)
>> Date: 2011-09-26 08:46
>>
>> Message:
>> The current behavior of halcmd is correct. According to the manpage,
>> "halcmd save" emits the current HAL configuration in the format of the
>> halcmd commands needed to reproduce it, so "=>" is the correct syntax for
>> nets. This behavior is verified by the "save.0" test in our test suite.
>>
>> Perhaps the confusion comes from the fact that in "halcmd show", nets are
>> displayed with two equals signs, "==>"? That may or may not be a problem
>> (i think it's not), but the current "halcmd save" output is definitely
>> correct.
>>
>>
>
> Perhaps the confusion, as you call it, is because no where in the EMC2
> documentation nor in the source code except in these two lines I
> identified, is the '=>' arrow mentioned. I don't really care that halcmd
> can manage to read in what it wrote out because of a cute trick in its
> parser. I care that the code conform to its documentation. Who knows, I
> might not be the only person to write my own code based on the
> documentation.
The halcmd manage is pretty explicit:
> net signame pinname ...
> Create signname to match the type of pinname if it does not
> yet exist.
> Then, link signame to each pinname in turn. Arrows may be
> used as in
> linkps.
And just above that:
> linkps pinname [arrow] signame
> (link pin to signal) Establishs a link between a HAL component
> pin pin‐
> name and a HAL signal signame. Any previous link to pinname
> will be bro‐
> ken. arrow can be "=>", "<=", "<=>", or omitted. halcmd
> ignores arrows,
> but they can be useful in command files to document the
> direction of data
> flow. Arrows should not be used on the command line since the
> shell might
> try to interpret them. Fails if either pinname or signame does
> not exist,
> or if they are not the same type type.
I don't know why halcmd sometimes uses two equals signs when printing arrows
for human consumption, but I think the docs clearly state that it expects one
equals signs on input, and thus produces one equal sign on output that's
designed for halcmd to parse.
> But please yourself.
Whatever dude….
--
Sebastian Kuzminsky <[email protected]>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
