From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 23 18:30:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C6E95EE for ; Sun, 23 Mar 2014 18:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B46BD773 for ; Sun, 23 Mar 2014 18:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s2NIU1CX076334 for ; Sun, 23 Mar 2014 18:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s2NIU1d9076333; Sun, 23 Mar 2014 18:30:01 GMT (envelope-from gnats) Date: Sun, 23 Mar 2014 18:30:01 GMT Message-Id: <201403231830.s2NIU1d9076333@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jilles Tjoelker Subject: Re: bin/187728: [patch] bc(1) should print error message to stderr X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Jilles Tjoelker List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Mar 2014 18:30:01 -0000 The following reply was made to PR bin/187728; it has been noted by GNATS. From: Jilles Tjoelker To: bug-followup@FreeBSD.org, ksmakoto@dd.iij4u.or.jp Cc: Subject: Re: bin/187728: [patch] bc(1) should print error message to stderr Date: Sun, 23 Mar 2014 19:20:25 +0100 In PR bin/187728, you wrote: > bc(1) should prints error message to stderr. POSIX seems to require this in interactive mode; in non-interactive mode, invalid input causes undefined behaviour. Note that the patch changes more than just the destination of the error message. The code in the repository prints the error message if and when dc reaches the point of the error, rather than immediately when the error is detected in the patched version. Since the patched version is simpler, it seems that the original code may be deliberately written that way. -- Jilles Tjoelker