Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68220 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68896 invoked from network); 19 Jul 2013 20:19:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jul 2013 20:19:19 -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.115 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.115 smtp115.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.115] ([108.166.43.115:34428] helo=smtp115.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/B1-13120-64F99E15 for ; Fri, 19 Jul 2013 16:19:18 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id C239B1B80AA; Fri, 19 Jul 2013 16:19:15 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 827C21B811E; Fri, 19 Jul 2013 16:19:15 -0400 (EDT) Message-ID: <51E99F47.90704@sugarcrm.com> Date: Fri, 19 Jul 2013 13:19:19 -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: Martin Amps CC: PHP Internals References: <091988B7-57E1-42E8-8DEF-D1657565B956@rtin.so> <51E8876C.6050301@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Compatibility changes for 5.5 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Understood. But given for the entire 5 series it was valid I feel people > finding their code randomly breaking now would expect to see it in the > documentation somewhere. It is still valid, and still works the same, just produces notice. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227