On Thu, Jul 19, 2012 at 11:06 AM, Rafael Dohms wrote:
> On Thu, Jul 19, 2012 at 12:03 PM, Charlie Somerville <
> char...@charliesomerville.com> wrote:
>
> > This has code readability problem written all over it. When maintaining
> it
> > also has problems, like with the bracket-less if's.
> > You
There is a Planet PHP which aggregates many blogs articles written by
contributors:
http://planet-php.net/
Peter
On Thu, Mar 8, 2012 at 09:58, adit adit wrote:
> Hi,
>
> Can you tell me which one of you guys has any blogs on which i can read
> about the php internals?
> I've already subscribed
whereas the query string and the fragment are part of the
latter.
See sections 3.3 and 5 of the RFC[1] for more information. Web
browsers and other user-facing software may accept this, but will
immediately update the displayed URL to a valid variant by inserting
the slash.
Regards,
Peter Beverlo
ng during at least another major
>>> before it gets removed.
>>
>> This makes much sense!
>
> Correct me if I'm wrong, but isn't T_VAR on class members already an
> E_STRICT warning? I thought it was...
>
> --Larry Garfield
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
No, the warning was removed in PHP 5.1.3.
Regards,
Peter Beverloo
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
VAR, considering it would
break huge amounts of userland code. In either case, it should be
deprecated with an E_DEPRECATED warning during at least another major
before it gets removed.
Regards,
Peter Beverloo
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ally don't rely on single keywords and will
be able to adapt a change like this without too much hassle.
On top of that, seeing that functions in classes are generally
referred to as methods, I believe removing the requirement would
improve consistency.
+1 from me.
Kind regards,
Peter Beverloo
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
opers will also use Javascript, likely
to be more appropriate for the web. Companies and individuals have
been adjusting their scripts in favor of PCRE[1][2][3], undeprecating
the extension seems senseless at this point.
I do think Philip Olson's proposal of adding a compile-time flag for
disabling e
Hello,
For what it's worth, a large +1 from me.
One concern I do have, however, is that the addition of scalar type hints
will put more attention to the lack of method overloading. Right now methods
can accept multiple values due to the type-lessness, and while it will
remain a possibility, c
