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
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
