[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-bug: [Bug 707064] Re: Remove unconnected net cues for netname connected nets
Krzysztof KoÅciuszkiewicz:
>Even if rewritten to be iterative, we would have to maintain a stack
>of visited net segments ourselves - in addition to a hash the current
>version uses. This might give us better control over memory usage and we
>could fail gracefully when allocation fails - but will likely complicate
>the function. Is gschem even run on systems where stack does not grow
>automatically?
The problem here is, that the size of the stack is usually set to some potentially "low" maximum.
It is usually enough, but I just recently came to the limitation. The program was just segfaulting at strange different locations. It is a pain to debug when you have no idea what are you dealing with.
Having own "stack" for this purpose is a bit more work, but can save a
lot of work later when you encounter problems.
This maximum exist at least on Linux and Windows.
--
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/707064
Title:
Remove unconnected net cues for netname connected nets
Status in GPL Electronic Design Automation tools:
New
Bug description:
This came up after a presentation with potential users.
The red cues on the end of unconnected net was perceeved as a nice
warning that something was unconnected.
Their expectation was that a net connected at one end should lose the
second cue (on its unconnected end) if the net is named. This could be
implemented either to mean "has a netname=" attribute, or that it is
connected to something which has one.
This helps to preserve the semantic that "red splodge" == something to
fix.
We also noted that the pin cues were not nearly as visible as they
ought to be when projected!
_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug