[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-bug: [Bug 810202] Re: gnetlist bom trips on missing attrib file
Hey Jared,
That's an awesome patch! I've got a few questions:
- Is it possible to specify an attribute containing a ',' in its name on the command line?
- What happens if backend-getopt raises an error (e.g. due to a missing argument to '-Oattribs')?
- What happens if an '-Oattribs' argument is specified, and an attribs file is also found or specified? My suspicion is that the "right thing" would be for the '-Oattribs' list to override rather than add to the list from the file...
Thanks for working on this!
** Changed in: geda
Importance: Undecided => Medium
** Changed in: geda
Status: New => In Progress
** Changed in: geda
Assignee: (unassigned) => Jared Casper (jaredcasper)
** Tags added: bom bom2 gnetlist
--
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/810202
Title:
gnetlist bom trips on missing attrib file
Status in GPL Electronic Design Automation tools:
In Progress
Bug description:
(as reported to geda-user by Girvin R. Herr)
If there is no attribs file around, the backends bom and bom2 crash
with an irritating error message on the command line:
/---------------------------------------
$gnetlist -g bom xx.sch
Loading schematic
[/home/gherr/projects/vds160/original/hardware/dac/docs/xx.sch]
Backtrace:
In current input:
1: 0* [bom "output.net"]
In /usr/local/share/gEDA/scheme/gnet-bom.scm:
37: 1 (let ((port #) (attriblist #)) (bom:printlist (cons #
attriblist) port) ...)
40: 2* [bom:parseconfig ...
40: 3* [open-input-file "attribs"]
In unknown file:
?: 4 [open-file "attribs" "r"]
<unnamed port>: In procedure open-file in expression (open-file str
OPEN_READ):
<unnamed port>: No such file or directory: "attribs"
\-------------------------------
Suggestions:
1) Check for the existence of the attribs file.
2a) Issue a newbie friendly message, if not.
2b) produce a sensible default attribs file on the fly.
3) accept a file name on the command line, so you can have different
attribs files for the same project
4) accept a string on the command line to replace the contents of the
attribs file
---<)kaimartin(>---
To manage notifications about this bug go to:
https://bugs.launchpad.net/geda/+bug/810202/+subscriptions
_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug