X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Fri, 10 Feb 2017 22:46:01 +0100 (CET) From: Roland Lutz To: "John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] large difference in gnetlist error message between versions. In-Reply-To: Message-ID: References: <31a96361-438d-a672-8be7-5984e989d74b AT ecosensory DOT com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-2053642908-1486763161=:27620" Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-2053642908-1486763161=:27620 Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 10 Feb 2017, Roland Lutz wrote: > your mail makes me aware of one thing I haven't thought about before: > gnetlist doesn't touch the output file any more if there were netlisting > errors because the generated file is probably broken and shouldn't > replace the old file. For DRC backends, however, it is probably > desireable to overwrite the existing output even if there were errors. > > How do you suggest solving this? Should a backend whose name starts > with “drc” always force an output file to be generated, even if there > have been netlisting errors? I committed a fix to master which implements this. gnetlist doesn't add a refdes=U? attribute to invalid symbols any more, though, in order to avoid subsequent errors. This means you wont't get a warning about a non-numbered part in the DRC output once the original error message has been printed. --8323329-2053642908-1486763161=:27620--