Hi,
I think traits will lend themselves to frequent runtime checking against the
type of class in which they were used. Consider a trait designed for use
with an Iterator class; the first thing might be to check the type of $this.
do you not think checks like this will be common / messy / perf
On Wednesday, December 08, 2010 6:05:05 am Loon, Reinier van wrote:
> > With that said, I like the idea of generalizing autoload to include
> > functions et al. Autoloading functions would make my life a lot easier.
> > :-)
>
> Yes, the alternative solution is to write a wrapper function:
> some
I did not see in the announce that you change the two weeks rule to a
single week. I really do not consider that going final today is the
right thing to do.
Maybe for 5.2 but it is definitively not the case for 5.3, have you
seen the amount of commits since last week? The recent security issue
rep
On Wed, 08 Dec 2010 19:13:08 -, Clint Byrum wrote:
On Wed, 2010-12-08 at 18:49 +, Gustavo Lopes wrote:
On Wed, 08 Dec 2010 15:10:30 -, Clint Byrum
wrote:
This example would be solved if during the lazy load you change the
php://input stream to point at the memory location tha
On Wed, 2010-12-08 at 18:49 +, Gustavo Lopes wrote:
> On Wed, 08 Dec 2010 15:10:30 -, Clint Byrum wrote:
>
> > On Wed, 2010-12-08 at 01:11 +, Gustavo Lopes wrote:
> >>
> >> For instance, current scripts can, in POST requests, read any number of
> >> times from php://input or $HTTP_RAW
On Wed, 08 Dec 2010 15:10:30 -, Clint Byrum wrote:
On Wed, 2010-12-08 at 01:11 +, Gustavo Lopes wrote:
For instance, current scripts can, in POST requests, read any number of
times from php://input or $HTTP_RAW_POST_DATA (to simplify, let's say we
even let go $HTTP_RAW_POST_DATA). Fo
On Wed, 2010-12-08 at 01:11 +, Gustavo Lopes wrote:
> On Wed, 08 Dec 2010 00:45:56 -, Tjerk Meesters
> wrote:
>
> > Don't have much knowledge about the internal workings of the engine, but
> > I'm wondering if it's possible to apply "lazy loading" to the $_POST
> > variable, so that
> __autoload() works fine if you have exactly one implementation for your entire
> system with exactly one set of logic for how to map a class name to a file
> name. As soon as you try to mix two different libraries together, fatal
> error.
>
> spl_autoload() does not suffer from this short-sighte
All, I made a RFC in the Wiki for autodefine.
http://wiki.php.net/rfc/autodefine
Cheers, Reinier
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
