Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85995 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56682 invoked from network); 28 Apr 2015 14:13:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Apr 2015 14:13:03 -0000 Authentication-Results: pb1.pair.com smtp.mail=mariano.iglesias@cricava.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mariano.iglesias@cricava.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain cricava.com from 209.85.217.182 cause and error) X-PHP-List-Original-Sender: mariano.iglesias@cricava.com X-Host-Fingerprint: 209.85.217.182 mail-lb0-f182.google.com Received: from [209.85.217.182] ([209.85.217.182:35162] helo=mail-lb0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/27-17556-B659F355 for ; Tue, 28 Apr 2015 10:13:00 -0400 Received: by lbbuc2 with SMTP id uc2so108203850lbb.2 for ; Tue, 28 Apr 2015 07:12:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cricava.com; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=fy3c3PtFvvVXtqepyq1sDEn8UDTAs8I3eoGEarvQcbw=; b=di3LFnZ1LkBFt7U+UhnDN0xKkDQ0322au9AV8jh5olqEQNRcMccZiMqiwIlFAAtcxP uEGmxCSG8P0R/hQryg66QZhlY5vDewg7mMsqjb5uQkVlBIBLdkDSsKD65q1lTHcxm5Rv 8czGu9CwOJkE7E9zF5MIJvyIEypOxS6woHCFg= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=fy3c3PtFvvVXtqepyq1sDEn8UDTAs8I3eoGEarvQcbw=; b=jF/i/xnz0EyWV6uNkEs166pVl7+vdf3raiQywzRGOTdJvq2SAT/wraZiqbG4D5KyIa CdviOFwfHoaxpMthL1jPGqsYDYF6WwhfCilHvqA57JLF7wqWKNf1eBNf3HWTgQy5XteD 2rmZDC81IqkmB2cpZmjTGsB7wIdAn1M8PRtRs3fc0rabtKJtO9w8qe/WzH26CItPfN5a H1Ss233EUFS/NelmPTG4Iklt2KKRDtf+cMCkvEQDyAstmXutavY3HbtgzaYbfxjdY12m qkasm+RTpOuc2lSX9eMoZdT6lL2duxuSwXkpWR+BlIz2mKXh3+GrS2YIjL2HIg0CDg04 BEyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=fy3c3PtFvvVXtqepyq1sDEn8UDTAs8I3eoGEarvQcbw=; b=Oe8QmkcyT18eBHZQHw2NOOHPGdcJApMFIVd4EDmVUX+VBJVhYa18OGZzjdpWT4xoAA 8oK3q7UPUPrQ6YrZX8H2j0inLI3e8qrD961NXjk2YtpWmr753hk5kGA4OmvmqUOwCclx pCHIiERzCtb8jzZGbkVMobfyLAAE5zTWgu/3GC4iRTdhm9gIAdx3hKSOkLRN9eVhlV8y cIqn3uE/2+0PK6ktUliymUh6ohrEPlSIGFxLIJl8dmeGRsTUbvEFYW63t3AkjrPazCdy PKQZxcVwE+37v0KQU9XHyiM/vCA3siPuKMWMsrHrEioRJ5zHVkVyQesuHxJ3E4PHk0rD wAhA== X-Gm-Message-State: ALoCoQlrKdFT3M32fVcUet5oiBTe4FsEGYrjS3NPM0aGncq3LiuQDKH2hQ96J50rhItWyUeeDkaT X-Received: by 10.152.207.105 with SMTP id lv9mr14918155lac.10.1430230376604; Tue, 28 Apr 2015 07:12:56 -0700 (PDT) MIME-Version: 1.0 Sender: mariano.iglesias@cricava.com Received: by 10.112.16.66 with HTTP; Tue, 28 Apr 2015 07:12:35 -0700 (PDT) In-Reply-To: <553F934B.5050201@gmail.com> References: <553DBEC4.7000609@gmail.com> <006c01d081a7$0e600640$2b2012c0$@php.net> <553F7818.1040402@gmail.com> <007601d081b8$36b9b490$a42d1db0$@php.net> <553F934B.5050201@gmail.com> Date: Tue, 28 Apr 2015 11:12:35 -0300 X-Google-Sender-Auth: h5jb6Pu6rhI6tnHUT6od4jCSeGM Message-ID: To: Rowan Collins Cc: internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Re: [RFC] Reserving More Types in PHP 7 From: mgiglesias@gmail.com (Mariano Iglesias) I do know about Lithium, but honestly Nate I don't agree with your complain. While I do understand the frustration of having to update code because of changes in the underlying platform (PHP7 in this case), I believe this is a change for the better, and to which dependent code should adapt. You have experienced this in the past yourself: wanting to introduce a new feature in a framework you developed sometimes implied BC changes which affected people who ended up not liking the fact that their code had to be modified. But BC changes are needed, and something as big as STH is definitely worth it. It is not by chance that its introduction and ultimately acceptance into the PHP core has been received with considerable excitement and energy. Yes, some (small portions) of userland PHP code, such as the Lithium framework (which by the way I probably have the biggest production code that utilizes it) will be affected. The solution for such frameworks? A simple class rename. Yes, that will imply that any Lithium based code that's not updated will not be supported by PHP7, but isn't that actually a good thing? Userland code should remain updated, moving forward with the language. On Tue, Apr 28, 2015 at 11:03 AM, Rowan Collins w= rote: > Fran=C3=A7ois Laupretre wrote on 28/04/2015 14:35: >> >> I am especially interested by the opinion of Drupal, Wordpress, and othe= r >> framework developers. Are there any out there ? Please comment. > > > If you look in the rest of the thread, you'll see a few: > > - Drupal's String class was part of Drupal 8, which is still in Beta, and > has been renamed/removed already > - AFAIK, Wordpress has never had a class with any of the newly reserved > names (most of their classes begin WP_) > - CakePHP has renamed "String" to "Text", and added an alias so both name= s > can be used in PHP5. Doesn't rule out them being interested in alternativ= e > solutions, though. > - The other framework mentioned as affected was Lithium, about which I kn= ow > nothing. > > Regards, > -- > Rowan Collins > [IMSoP] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >