Pierre Joye wrote:
Hi Dmitry,
From a BC point of view, the impact will be minimal. The only project
I found relying on this syntax is XPath class [1].
I'm wondered why they use it, because their var ($parseBlock) is always 1.
Please add a note the upgrade guide as well in trunk, maybe in
Hi Dmitry,
>From a BC point of view, the impact will be minimal. The only project
I found relying on this syntax is XPath class [1].
Please add a note the upgrade guide as well in trunk, maybe in a BC
break sections.
[1] http://google.com/codesearch?hl=en&sa=N&q=lang:php+break\s{1,}%28\%24\w%2
On Wed, 24 Nov 2010, Dmitry Stogov wrote:
> the proposed patch (backport from php6) is attached.
> I think this feature is completely useless and it was agreed to remove it
> about 5 years ago.
>
> Derick, can I commit the patch today?
Sure. You know this stuff best :-)
cheers,
Derick
--
http
the proposed patch (backport from php6) is attached.
I think this feature is completely useless and it was agreed to remove
it about 5 years ago.
Derick, can I commit the patch today?
Thanks. Dmitry.
Dmitry Stogov wrote:
Hi,
Previously we decided to remove "break/continue $var" syntax.
I ev
Hi!
Previously we decided to remove "break/continue $var" syntax.
I even implemented it in PHP6 brunch, however it wasn't backported into
trunk. Could I do it?
I think it's fine to remove it.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
2010/11/18 Dmitry Stogov
> Hi,
> Previously we decided to remove "break/continue $var" syntax.
> I even implemented it in PHP6 brunch, however it wasn't backported into
> trunk. Could I do it?
>
>
+1 to removing it.
--
Regards,
Felipe Pena
Hi,
Previously we decided to remove "break/continue $var" syntax.
I even implemented it in PHP6 brunch, however it wasn't backported into
trunk. Could I do it?
Thanks. Dmitry.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
