gnetlist doesn't detect duplicate refdes

Bug #698367 reported by ahvezda
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gEDA
Won't Fix
Low
Unassigned

Bug Description

gnetlist (I've used the PCB frontend) does not detect
duplicate refdes.

-------snip-----------
werner@work:~/daten/elektronik> grep R11 output.net
unnamed_net23 R11-2 Q1-B
unnamed_net19 S2-1 R11-2
unnamed_net6 R11-1 R8-1 U1-18
Z0 R11-1 U1-2
-------snip-----------

Question is, should gnetlist recognize and warn about
duplicate refdes?

Changed in geda:
status: New → Won't Fix
Revision history for this message
KaiMartin (kmk-familieknaak) wrote :

Currently, gnetlistg has no way to know, whether, or not a duplicate refdes is legitimate. There are various use cases that involve duplicate refdes. (slotted symbols, components with power supply split into a different symbol, components with large pin count split into parts, ...)

---<)kaimartin(>---

Revision history for this message
Ethan Swint (eswint-ramu) wrote : Re: gEDA-bug: [Bug 698367] Re: gnetlist doesn't detect duplicate refdes

On 08/23/2011 02:21 AM, KaiMartin wrote:
> Currently, gnetlistg has no way to know, whether, or not a duplicate
> refdes is legitimate. There are various use cases that involve duplicate
> refdes. (slotted symbols, components with power supply split into a
> different symbol, components with large pin count split into parts, ...)
>
It would be really nice if, when a duplicate refdes was found, that the
system would provide some notification and/or ask permission to link the
symbols. That would require a unique ID attribute be assigned to each
symbol, then their could be a delimited list of 'linked' IDs as a second
new attribute. This would also provide a method to preserve
autonumbering across split components/symbols. ('No the op-amp in the
bottom-left corner *needs* to be on the same chip as the op-amp on the
bottom-right. DFNSDK GM HG SHK gnetlist!!!')

-Ethan

Revision history for this message
Peter TB Brett (peter-b) wrote :

This is a feature, not a bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.