delorie.com/archives/browse.cgi | search |
> The excuse is that doing that will lead to bugs. The context was "what should gnetlist allow?" The answer is: everything it can. If the downstream tools have limits, let them manage those limits themselves. Why should gnetlist, or even a netlist backend, limit what *it* can handle, if it doesn't have to? If I change the pcbfwd netlister to fail on '$' for some then-valid reason in pcb, and pcb itself changes to allow '$', I have to go back and "fix" the netlister (and possibly older but previously installed netlisters) to allow it. There's no reason for that. If the user puts it in the schematic, and the netlister *can* pass it downstream, it *should*.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |