On Sat, 15 Aug 2009 09:24:54 -0600, John Doty wrote:
Again: Do you seriously believe that a decent backend should care about
the order the user has entered symbols in gschem? If so, please give an
example case.
No it should not.
Fine.
So there is no reason to shout at me if I intend to
On Aug 17, 2009, at 11:51 AM, Kai-Martin Knaak wrote:
On Sat, 15 Aug 2009 09:24:54 -0600, John Doty wrote:
Again: Do you seriously believe that a decent backend should care
about
the order the user has entered symbols in gschem? If so, please
give an
example case.
No it should not.
On Sat, Aug 15, 2009 at 5:12 AM, al davisad...@freeelectron.net wrote:
A netlister needs to work for all symbols. No exceptions.
Why? Should it work even for symbols without models or incompatible
models (e.g. verilog RTL in an analog AC simulation)?
For
Spice format, you can go nuts with
On Saturday 15 August 2009, r wrote:
On Sat, Aug 15, 2009 at 5:12 AM, al
davisad...@freeelectron.net wrote:
A netlister needs to work for all symbols. No exceptions.
Why? Should it work even for symbols without models or
incompatible models (e.g. verilog RTL in an analog AC
simulation)?
On Aug 13, 2009, at 6:15 PM, Kai-Martin Knaak wrote:
On Sun, 09 Aug 2009 17:43:07 -0600, John Doty wrote:
You mean, the behavior of a netlister should depend on the order of
components in the *.sch file? Please give an example if you
seriously
think so.
No. The order isn't the issue.
On Saturday 01 August 2009, A.Burinskiy wrote:
And, finally, me, as a user, will not be happy to change the
script each time I add new symbol!
Good thing you mentioned it.
Unfortunately, the Spice format is very irregular, so dealing
with it is pure hell. That is one of the reasons for
On Sun, 09 Aug 2009 17:43:07 -0600, John Doty wrote:
You mean, the behavior of a netlister should depend on the order of
components in the *.sch file? Please give an example if you seriously
think so.
No. The order isn't the issue.
Yes, it is. Currently gnetlist behaves differently on
On Aug 9, 2009, at 9:59 PM, A.Burinskiy wrote:
John,
Do you mean that one day source= attribute is reference to schematic,
another day it is something else?
No, I mean that many back ends need to see a flat netlist, while in
the future others will need to see the hierarchy. The ones that
On 08/10/2009 06:03 AM, John Doty wrote:
On Aug 9, 2009, at 9:59 PM, A.Burinskiy wrote:
John,
Do you mean that one day source= attribute is reference to schematic,
another day it is something else?
No, I mean that many back ends need to see a flat netlist, while in
the future
On Aug 10, 2009, at 8:19 AM, A.Burinskiy wrote:
On 08/10/2009 06:03 AM, John Doty wrote:
On Aug 9, 2009, at 9:59 PM, A.Burinskiy wrote:
John,
Do you mean that one day source= attribute is reference to
schematic,
another day it is something else?
No, I mean that many back ends need
John,
It is not a big deal to write a parser. The big deal is creating
meaningful language. Flexible enough, yet not overloaded with features,
transparent and logical, understandable not only for designer, but to
end user too. My problem is that I'm newbee for the PCB. Just started
using
On Aug 10, 2009, at 9:46 AM, A.Burinskiy wrote:
John,
It is not a big deal to write a parser. The big deal is creating
meaningful language.
Don't need to create a language, plenty of those around. Just need to
choose one that won't frighten the timid. And need a set of functions.
On Sat, 01 Aug 2009 10:16:07 -0600, John Doty wrote:
Just about any language works naturally on Unix these days,
Not quite. C can draw on a host of system functions and libs that no
other environtment variables, inter process communication via dbus and
the various ways to interact with the
On Aug 9, 2009, at 3:19 PM, Kai-Martin Knaak wrote:
For me that's not the issue: the issue is that you're putting yet
another gnetlist behavior out of reach of back end control.
You mean, the behavior of a netlister should depend on the order of
components in the *.sch file? Please give
John,
Do you mean that one day source= attribute is reference to schematic,
another day it is something else? We have to stick to some reasonable
meaning of all attributes, at list to be able to exchange libraries and
collect our work over the years, isn't it?
Talking about ynetlist: it has
On Fri, Jul 31, 2009 at 8:49 PM, A.Burinskiyalexb...@gmail.com wrote:
Dear gEDA community members,
I created yet another netlister for gschem. Netlister supports flattened
or hierarchical netlist, handles slotting and global net names. Will be
glad to hear any feedback. The source located in:
On Aug 1, 2009, at 4:17 AM, r wrote:
On Fri, Jul 31, 2009 at 8:49 PM, A.Burinskiyalexb...@gmail.com
wrote:
Dear gEDA community members,
I created yet another netlister for gschem. Netlister supports
flattened
or hierarchical netlist, handles slotting and global net names.
Will be
Hi R,
I thought about implementing some language for netlist and after all I
decided to go with plain C++ and get rid of using device attribute
unless it is absolutely necessary (such as input/output pin) and give
more strength to user symbol definition relying on the fact that end
user knows
On Sat, Aug 1, 2009 at 2:49 PM, A.Burinskiyalexb...@gmail.com wrote:
I thought about implementing some language for netlist and after all I
decided to go with plain C++ and get rid of using device attribute
unless it is absolutely necessary (such as input/output pin) and give
more strength to
On Sat, Aug 1, 2009 at 2:37 PM, John Dotyj...@noqsi.com wrote:
Hmm, I think Guile is fine for gnetlist's purposes. A minor problem
has been backward compatibility, leading to dependency hell. The
people who package the distros have this under better control than
they did a few years ago.
On Sat, 01 Aug 2009 11:17:10 +0100, r wrote:
I'm a bit puzzled that all of you tend to choose C/C++ for implementing
your tools.
like ist, or not, C is the lingua franca of computer science. I have yet
to meet an IT professional, who has never written any C code. In
addition, C is the
On Aug 1, 2009, at 9:21 AM, r wrote:
Well, I see several other problems here as well:
1. Guile (as a Scheme implementation) is not particularly well
supported, this leads to dependency hell and missing/incomplete
wrappers for modern libraries (like gtk2 - not really a problem for
gnetlist
On Aug 1, 2009, at 10:03 AM, Kai-Martin Knaak wrote:
On Sat, 01 Aug 2009 11:17:10 +0100, r wrote:
I'm a bit puzzled that all of you tend to choose C/C++ for
implementing
your tools.
like ist, or not, C is the lingua franca of computer science. I
have yet
to meet an IT professional,
On Sat, Aug 1, 2009 at 5:09 PM, John Dotyj...@noqsi.com wrote:
Perhaps not Guile, but we're going to have to keep Scheme around for
a long time, because all those back ends are important. It's not that
there's a lot of code in them, but they embody a great deal of
research into just what each
On Aug 1, 2009, at 11:45 AM, r wrote:
On Sat, Aug 1, 2009 at 5:09 PM, John Dotyj...@noqsi.com wrote:
Perhaps not Guile, but we're going to have to keep Scheme around for
a long time, because all those back ends are important. It's not that
there's a lot of code in them, but they embody a
Dear gEDA community members,
I created yet another netlister for gschem. Netlister supports flattened
or hierarchical netlist, handles slotting and global net names. Will be
glad to hear any feedback. The source located in:
http://sourceforge.net/projects/ynetlist/files/
Thanks,
Alex.
On Fri, 31 Jul 2009 12:49:57 -0700, A.Burinskiy wrote:
I created yet another netlister for gschem. Netlister supports flattened
or hierarchical netlist, handles slotting and global net names. Will be
glad to hear any feedback. The source located in:
Wow another netlister, that makes 4 now?
gnetlist
spnet
gnetman
ynetlist
At least gEDA users have plenty of choices now.
On Fri, Jul 31, 2009 at 12:49 PM, A.Burinskiyalexb...@gmail.com wrote:
Dear gEDA community members,
I created yet another netlister for gschem. Netlister supports
Actually there is option for ynetlist -g{pcb,spice}. I do output for
PCB, but it is a very first cut. I do not know output format that I have
to use. Try this option, type
ynetlist -gpcb filename.sch
Then send me comments and I will correct output to be the right one.
Please let me know tool
Actually only one: gnetlist could be found from gEDA site. All others
have to be tested and if it suits purpose offered for download from gEDA
site.
On 07/31/2009 03:45 PM, Anthony Shanks wrote:
Wow another netlister, that makes 4 now?
gnetlist
spnet
gnetman
ynetlist
At least gEDA users
A.Burinskiy wrote:
Dear gEDA community members,
I created yet another netlister for gschem. Netlister supports flattened
or hierarchical netlist, handles slotting and global net names. Will be
glad to hear any feedback. The source located in:
Dan,
No doubt, we need someone to identify week and strong parts of various
netlisters and choose one-two for support. As to me, I was trying
gnetlist and spnet (I was unaware of gnetman). Non of them did worked
fine for me. That was a reason I wrote netlister for myself, then
consider that
32 matches
Mail list logo
