On a related note, there's a feature that I quietly added to 'comp' on
TRUNK that may be useful here.
One problem that was mentioned elsewhere in the thread is that you not
only have to set the number of 'or2' instances at the load-time of or2,
but you have to agree on the numbering everywhere.
The still-hypothetical 'newinst' would be a way around both of these
problems, but, well, it's still hypothetical.
So, anyway, the half-solution I added is the 'names=' parameter for a
comp-generated component. Suppose you have two hal snippets that both
use 'or2' instances:
# snippet 1
loadrt or2 count=2
net A1 => or2.0.in0
net A2 => or2.1.in0
...
# snippet 2
loadrt or2 count=2
net B1 => or2.0.in0
net B2 => or2.1.in0
...
To use them both together, you have to delete one loadrt line and change
the other to
loadrt or2 count=4
then renumber things:
# snippet 1
net A1 => or2.0.in0
net A2 => or2.1.in0
# snippet 2
net B1 => or2.2.in0
net B2 => or2.3.in0
With names= you can write this:
loadrt or2 names=or2.A1 or2.A2 or2.B1 or2.B2
# snippet 1
net A1 => or2.A1.in0
net A2 => or2.A2.in0
# snippet 2
net B1 => or2.B1.in0
net B2 => or2.B2.in0
When snippets use this style, you only have to modify the 'loadrt' line
to specify the new names; the snippets don't have to be touched.
Will names= help users enough that we should commit to having it in 2.3?
We should decide soon whether to leave this in or revert it.
Jeff
PS can anybody remind me of the status of 'halcmd alias' in TRUNK?
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
