From owner-freebsd-bugs Tue Jul 20 21:50: 6 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3321415430 for ; Tue, 20 Jul 1999 21:50:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA14997; Tue, 20 Jul 1999 21:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 20 Jul 1999 21:50:02 -0700 (PDT) Message-Id: <199907210450.VAA14997@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mitsuru IWASAKI Subject: Re: kern/12663: Ambiguous if statement Reply-To: Mitsuru IWASAKI Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/12663; it has been noted by GNATS. From: Mitsuru IWASAKI To: Nate Williams Cc: freebsd-gnats-submit@freebsd.org, adamw@holonet.net Subject: Re: kern/12663: Ambiguous if statement Date: Wed, 21 Jul 1999 13:40:00 +0900 Nate Williams writes: > No, they could not break silently, as the syntax is guaranteed to be > correct by the ANSI-C standard. If it broke, the compiler would be > broke and a number of other such code in many systems would also break. You might be right, Nate. But I forgot to fix it up when I ported the code from NetBSD's one. Also I like a lot the style as Mr. Adam Wight pointed out because It is preventible from missing { and } when few more lines are needed in the block afterward. Thank you Adam and Nate, I'll fix it soon if there is no objections. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message