On Sunday 20 November 2005 23:18, George Schlossnagle wrote:
> Doesn't work to well with
>
> $$moo{1};
Didn't think of that :)
> or
>
> $moo = array( 1 => 'foo');
> $moo{1};
I actaully didn't even know you could do that :)
So.. ignore my regex, but not my comment about decent docmentation for
Ian P. Christian wrote:
On Sunday 20 November 2005 22:27, Ian P. Christian wrote:
If this change included a simple sed command that could be applied to code
to fix 'legacy' code
Sorry, should have included this...
For example:
$ cat test
$ sed -e 's/$\([a-zA-Z][a-zA-Z0-9]*\){\(
On Sunday 20 November 2005 22:27, Ian P. Christian wrote:
> If this change included a simple sed command that could be applied to code
> to fix 'legacy' code
Sorry, should have included this...
For example:
$ cat test
$ sed -e 's/$\([a-zA-Z][a-zA-Z0-9]*\){\([0-9]*\)}/substr($\1,\2,1)/g' test
On Sunday 20 November 2005 22:21, Christian Schneider wrote:
> I second that as people on the list here are undecided about the removal
> of {} for strings. Keeping that warning creates even more confusion
> about a really minor issue (having two ways of accesing strings offsets).
Whilst I'm not r
Sascha Schumann wrote:
16 Nov 2005, PHP 5.1 Release Candidate 5
- Added an E_STRICT warning on the usage of {} for accessing of string
offsets.
(Ilia)
I suggest removing that warning immediately until the matter
is resolved.
I second that as people on the list here are undecided abou
Rasmus Lerdorf wrote:
The PHP 6 stuff is still up in the air. The original suggestion was to
carry through with the deprecation of [] which I strongly vetoed since
it would break everything. We can revisit whether we want to remove {}
in PHP 6. I didn't think people had such strong feelings
> I suggest removing that warning immediately until the matter
> is resolved.
+1 ( times the discount-for-rants-factor )
-mp
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
16 Nov 2005, PHP 5.1 Release Candidate 5
- Added an E_STRICT warning on the usage of {} for accessing of string
offsets.
(Ilia)
I suggest removing that warning immediately until the matter
is resolved.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
> For the 13th time. {} is not going away in 5.1.
>From the NEWS file:
16 Nov 2005, PHP 5.1 Release Candidate 5
- Added an E_STRICT warning on the usage of {} for accessing of string
offsets.
(Ilia)
That is, code that has been tested with RC4 and that worked (not even a
notice on whatever err
Maybe you have spoken to the wrong people then. Since {} has
been advocated for quite some time as the Right Way to access
string offsets, basically all PHP books teach that syntax.
As such {} is used very frequently. There are vast amounts
of code with that syntax. Breaking
The PHP 6 stuff is still up in the air. The original suggestion was to
carry through with the deprecation of [] which I strongly vetoed since
it would break everything. We can revisit whether we want to remove {}
in PHP 6. I didn't think people had such strong feelings about it.
From my chec
Hey, you're still alive?
Alive and kicking.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 18 Nov 2005, Sascha Schumann wrote:
> And it really should not be going away in PHP 6 either. I
> don't get why you are suggesting to expend so many resources
> as part of a migration effort while it is obvious that there
> are no advantages at all in dropping {}. It make
And it really should not be going away in PHP 6 either. I
don't get why you are suggesting to expend so many resources
as part of a migration effort while it is obvious that there
are no advantages at all in dropping {}. It makes no sense.
- Sascha
On Fri, 18 Nov 2005, Rasm
Matthias Pigulla wrote:
Even the attempt of trying to change or remove some language feature
like the {} thing IN A RC5 is unbelievably unprofessional.
For the 13th time. {} is not going away in 5.1.
-Rasmus
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:
Anybody interested in my two cents? (I shouldn't have asked as I'm going
to tell you anyway.)
"You will break many more scripts by dropping [] for strings than the
other way around. Do you agree?" - Heck, this sounds as if you're doing
a "let's drop stuff for some technical reason no average PH
16 matches
Mail list logo
