Mail Archives: geda-user/2015/10/19/14:58:37
> Well, I think that's a logical requirement, not a mere desire.
I'm glad you agree with yourself. We're back to my original
supposition, that *if* it's required, *one* of the options is a UUID.
> > No, (3) only requires a UUID be assigned to each symbol as it's instantiated.
>
> Until you realize that users make copies of things using multiple
> methods, and the intent of the copy may be to move the circuitry or
> to duplicate it. Then, it still requires clairvoyance.
We've discussed this in the past, and generally agree that "path to
object in design" needs to be part of the uniqueness, in order to
differentiate between one symbol showing up in multiple places in a
heirarchy. This plus "unique on page" (as long as the key to
uniqueness doesn't change over time) is probably sufficient to
uniquely correlate an instance in <downstream> to one symbol in the
project. But we also generally agreed that a heirarchical schematic
would need to be flattened to produce an as-built anyway, which limits
that problem somewhat.
- Raw text -