> A few months ago I thought geda lacks of a good DRC checker, to check > things like the ones you mention. > Then, I wrote a DRC gnetlist backend, which is now included in gnetlist > distribution as gnet-drc2.scm . > I think it's quite complete, so maybe you want to have a look at it > before writing another one. There's always room for improvement.
Carlos, Prompted by your posting, I went and looked at drc2. I have been thinking about DRC checking for a while, and wanted something to check the parameters you check. Your prog is excellent work! It found a funky issue with one of my schematics (doubly named net) which I had overlooked. One question: When I ran it, it complained vociferously about parts lacking the slot attribute. None of my parts are multislotted; most of them are simple surface-mount passives. Therefore, I don't need this check. I read the comments in the scheme file about how to enable/disable various checks. I am a little confused about how to do this, except to stick a (define action-unused-slots \#c) somewhere in the scheme prog. I tried to put this define into the gnetlistrc file, but that didn't work. (Ales, as a parenthetic comment, I tried netlisting with the -r flag set, as described on the man page, but that barfed, saying "invalid option -- r". If this is a known bug, please excuse my raising the issue. If it is not known, then perhaps I will fix it . . . .) Therefore, my question is: where does the define go? Are you assuming that we run gnetlist in interactive mode? A suggestion: if the "define" could live in the gnetlistrc file, that would be a fine thing. You could also enable/disable various checks using the command-line flag passing facility I put into gnetlist.scm if you wanted, although I think that this would be cumbersome because there are so many possible checks. . . . Thanks for your help, Stuart
