Mail Archives: geda-user/2015/10/21/14:46:34
> >>> If the tool *requires* that each symbol be unique, then either...
> >>>
> >>> 1. It must not let the user provide non-unique symbols, or
> >>>
> >>> 2. It must produce a hard error when it detects non-unique symbols, or
> >>>
> >>> 3. It must provide some user-independent way of making the symbols unique.
> >>>
> >>> gaf currently does none of these.
> What common rules separate valid schematics from invalid for *every*
> flow? No, I don't know either. I'm generally not willing to inflict
> rules that apply only to the subset of flows I know on
> everybody. Are you?
I never said there were common rules, although it would be nice if
there were. I never said those rules had to be applied globally,
although that would simplify training.
What I said was that *if* a tool has a requirement, it needs to
somehow enforce that requirement. Perhaps not all backends require
refdes's to be unique, but those that do should somehow require it
more than just via some hidden recommendation. Perhaps for those
backends, my option #2 is the right solution. That doesn't invalidate
my original list, either - there are multiple ways of "enforcing" what
a tool actually requires, even if those ways might not be appropriate
for our particular implementation.
> Here's an alpha gnetlist back end that detects duplicate refdes-pin
> combinations,
Ok, good. How do we integrate that with the backends that require
uniqueness? Do we somehow have a library of "helper" plugins that the
netlister can offer to backends?
- Raw text -