gEDA-bug: [Bug 810202] Re: gnetlist bom trips on missing attrib file

[Jared Casper <jaredcasper@xxxxxxxxx>]

1.  No, I chose the comma as the delimiter for simplicity.  I guess we
could check for an escaped comma or something but it didn't seem worth
it.  I'm not familiar with Guile's string processing, but it's possible
there is something smarter than string-split.

2.  backend-getopt print out the error message, which includes a
backtrace (I guess because of the use of scm-error?).  Things exit out
gracefully after that as far as I can tell.  The backtrace makes the
error message seem a little more intimidating, but last line should be
reasonable (e.g. "Backend options 'attribs' requires an argument")

3. -Oattribs takes precedence and overrides anything in the file (either
attribs or a specified file).

-- 
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