Re: [tap] Parse error vs failure
Andy Armstrong <andy@hexten.net> Mon, 02 February 2009 12:15 UTC
Return-Path: <tap-bounces@ietf.org>
X-Original-To: tap-archive@ietf.org
Delivered-To: ietfarch-tap-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99F5F28C12C; Mon, 2 Feb 2009 04:15:36 -0800 (PST)
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 342D828C13A for <tap@core3.amsl.com>; Mon, 2 Feb 2009 04:15:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHgxaVGAoSWF for <tap@core3.amsl.com>; Mon, 2 Feb 2009 04:15:35 -0800 (PST)
Received: from post.hexten.net (post.hexten.net [75.127.65.154]) by core3.amsl.com (Postfix) with ESMTP id 8798328C12C for <tap@ietf.org>; Mon, 2 Feb 2009 04:15:32 -0800 (PST)
Received: from voodoo.ripley (ca93nt.hexten.net [82.152.157.85]) by post.hexten.net (Postfix) with ESMTP id E9CFE6CBC4C; Mon, 2 Feb 2009 12:15:01 +0000 (GMT)
Message-Id: <9AC77404-FBC1-4292-AC47-5B6E5D9B628E@hexten.net>
From: Andy Armstrong <andy@hexten.net>
To: Michael G Schwern <schwern@pobox.com>
In-Reply-To: <4984B200.6060907@pobox.com>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 02 Feb 2009 12:15:00 +0000
References: <4984B200.6060907@pobox.com>
X-Mailer: Apple Mail (2.930.3)
Cc: tap@ietf.org
Subject: Re: [tap] Parse error vs failure
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: tap-bounces@ietf.org
Errors-To: tap-bounces@ietf.org
On 31 Jan 2009, at 20:18, Michael G Schwern wrote: > Consensus? Generally prefer failure-with-warning over parse error > for valid > but sort of nonsense output? Yeah, they're semantic rather than syntactic errors. -- Andy Armstrong, Hexten _______________________________________________ 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