Re: [tap] Parse error vs failure

Steffen Schwigon <ss5@renormalist.net> Sun, 01 February 2009 00:58 UTC

To: tap@ietf.org
References: <4984B200.6060907@pobox.com> <20090131213720.GB30031@klangraum.plasmasturm.org> <4984F0E4.8090001@plusthree.com>
From: Steffen Schwigon <ss5@renormalist.net>
Date: Sun, 01 Feb 2009 01:58:32 +0100
In-Reply-To: <4984F0E4.8090001@plusthree.com> (Michael Peters's message of "Sat, 31 Jan 2009 19:46:28 -0500")
Message-ID: <87pri3vupz.fsf@renormalist.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Subject: Re: [tap] Parse error vs failure
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org

Michael Peters <mpeters@plusthree.com> writes:
> Aristotle Pagaltzis wrote:
>> * Michael G Schwern <schwern@pobox.com> [2009-01-31 21:20]:
>>> Generally prefer failure-with-warning over parse error for
>>> valid but sort of nonsense output?
>> Basically. I think we should differentiate between syntactical
>> and semantic errors.
>
> I agree. Syntax errors should be parse errors, but semantic errors should be failure-with-warning.

+1 Me too.

Steffen
-- 
Steffen Schwigon <ss5@renormalist.net>
Dresden Perl Mongers <http://dresden-pm.org/>
German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
_______________________________________________
tap mailing list
tap@ietf.org
https://www.ietf.org/mailman/listinfo/tap

[tap] Parse error vs failure Michael G Schwern
Re: [tap] Parse error vs failure Aristotle Pagaltzis
Re: [tap] Parse error vs failure David E. Wheeler
Re: [tap] Parse error vs failure Michael Peters
Re: [tap] Parse error vs failure Steffen Schwigon
Re: [tap] [offlist] Re: Parse error vs failure Aristotle Pagaltzis
Re: [tap] Parse error vs failure Ovid
Re: [tap] Parse error vs failure Steffen Schwigon
Re: [tap] Parse error vs failure Aristotle Pagaltzis
Re: [tap] Parse error vs failure Andy Armstrong
Re: [tap] Parse error vs failure Andy Armstrong
Re: [tap] Parse error vs failure Michael G Schwern
Re: [tap] Parse error vs failure Steffen Schwigon