[snip]
Yeah, sure. This is no problem as long as you are aware of it. But I
just spent one day looking for errors in my netlister-backend.
I still think this is a strange behavior.
I spent a little time looking at this during the code sprint.
This is a limitation of how gnetlist finds
[snip]
Your are correct the produced netlist is incorrect.
The last two nets unnamed_net2 and unnamed_net1 should have been
combined.
I will look at this bug/behavior during the code sprint
happening on Sunday.
-Ales
I guess I don't see how shorting around a circuit involves connecting
two nets which don't connect to anything else. Can you post a
simplified version of what you are trying to do? We can look at it
during the code sprint.
Meanwhile, why not stick a zero ohm resistor into the shorting net,
On 7/20/06, Stuart Brorson [EMAIL PROTECTED] wrote:
Just out of curiosity, why would you want to have two nets which
connect to nothing other than each other?
Before we label it a bug, what is the goal of this construct?
My goal was to avoid snaking wires to connect subcircuits.
Here are
Ok. I am not sure what that means as I am not familiar with the PCB backend.
What happens if you run in on the top-level file (top.sch), which
includes test.sch as a subnet?
/Arvid
Steve Meier skrev:
When I run gnetlist -gPCB test.sch -o test.net I get
unnamed_net3R34-2 4-1
unnamed_net2
send me your test1.sym and I will run it for you.
Steve Meier
On Thu, 2006-07-20 at 18:43 +0200, Arvid Rosén wrote:
Ok. I am not sure what that means as I am not familiar with the PCB backend.
What happens if you run in on the top-level file (top.sch), which
includes test.sch as a subnet?
Steve Meier skrev:
send me your test1.sym and I will run it for you.
Steve Meier
Oh, I forgot to include it. Sorry.
Here it is!
/Arvid
On Thu, 2006-07-20 at 18:43 +0200, Arvid Rosén wrote:
Ok. I am not sure what that means as I am not familiar with the PCB backend.
What happens if
Arvid,
Your are correct the produced netlist is incorrect.
The last two nets unnamed_net2 and unnamed_net1 should have been
combined.
As previously demonstrated the net list for test.sch is correct and so I
suspect the bug is in the code where the the hierarchical boundary is
crossed to
Steve,
Thanks for confirming my suspicion.
Should I report this somewhere, or is this list enough? I'm not familiar
with how the gEDA development is handled.
/Arvid
Steve Meier skrev:
Arvid,
Your are correct the produced netlist is incorrect.
The last two nets unnamed_net2 and
9 matches
Mail list logo