Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68259 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45746 invoked from network); 20 Jul 2013 07:37:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jul 2013 07:37:31 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.75 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.75 smtp75.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.75] ([108.166.43.75:56983] helo=smtp75.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 10/50-13120-93E3AE15 for ; Sat, 20 Jul 2013 03:37:30 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 75DFD1E8183; Sat, 20 Jul 2013 03:37:27 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 285441E8074; Sat, 20 Jul 2013 03:37:27 -0400 (EDT) Message-ID: <51EA3E36.1090402@sugarcrm.com> Date: Sat, 20 Jul 2013 00:37:26 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Yasuo Ohgaki CC: "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Operator precedence is undefined? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I cannot believe this is true now, but I ask list before I fix doc. I don't think there's something that needs to be fixed. "Undefined" means "it depends on implementation and we do not want to commit to a specific behavior here because implementations may change". This is a fair warning against using implementation details that are not promised to stay fixed and later crying why next PHP version broke your code. Because you used undefined behavior. If the behavior is specified as undefined, that means "don't do this" - so you know it may be broken, and write better code instead that is not broken. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227