X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Envelope-From: paubert AT iram DOT es Date: Fri, 15 Aug 2014 23:55:58 +0200 From: Gabriel Paubert To: geda-user AT delorie DOT com Subject: Re: [geda-user] rs-274x nits Message-ID: <20140815215557.GB5149@visitor2.iram.es> References: <53EA540E DOT 9000609 AT sonic DOT net> <1407876579 DOT 79247 DOT YahooMailNeo AT web120502 DOT mail DOT ne1 DOT yahoo DOT com> <53EA8692 DOT 4090902 AT sonic DOT net> <1407882017 DOT 64999 DOT YahooMailNeo AT web120501 DOT mail DOT ne1 DOT yahoo DOT com> <57B5BB87-4F51-4279-B689-8229896512DD AT noqsi DOT com> <53EADD10 DOT 40806 AT sonic DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <53EADD10.40806@sonic.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spamina-Bogosity: Unsure X-Spamina-Spam-Score: -0.2 (/) X-Spamina-Spam-Report: Content analysis details: (-0.2 points) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.4989] 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 On Tue, Aug 12, 2014 at 08:35:44PM -0700, Dave Curtis wrote: > On 08/12/2014 04:19 PM, John Doty wrote: > > > >On Aug 12, 2014, at 4:57 PM, Dave Curtis wrote: > > > >>Because if "CR and LF have no effect", then why the admonition against CR/LF against places after a comma? > > > >Often, specs for readers say “be liberal in what you accept” while specs for writers say “be conservative in what you emit”. That seems to be the case here. Don’t make a big deal of it. > > > > Yes, I totally understand that philosophy. If I was writing a > reader, I would have no problem being liberal. If I was writing a > writer, I would have no problem being conservative. But... I am > writing a validation tool, which leaves zero margin for lack of > precision. > > I first did logic design on mainframe CPU's in 1981. I spent a large > part of my life combing architecture documents for nits, making the > lives of the spec authors quite miserable until they told me > precisely what they meant. Logic design mistakes in CPUs can be > expensive. At one point in my life I signed off on the Pentium > processor errata sheet every month before it went out..... And it still was mass-produced with some "floating point division issues" ;-) Gabriel