Re: [PHP-DEV] Re: [fw-webservices] Re: [PHP-DEV] RFC - "class underloading" -or- "ancestor overloading"

2010-03-15 Thread Richard Quadling
On 15 March 2010 21:43, Larry Garfield wrote: > On Monday 15 March 2010 03:08:28 pm Nate Gordon wrote: > >> > If there were a syntactic-level support for "wrap this object in this >> > class and pass through any method that isn't redefined", a sort of >> > sideways extends, >> > that would become

Re: [PHP-DEV] Where are we ACTUALLY on Unicode?

2010-03-15 Thread Stanislav Malyshev
Hi! What I am probably asking is what was the brick wall PHP6 hit. I was under the impression that there was no agreement on 'switchable or only' to unicode core? ( And those who did write PHP6 books seemed to have their own views on which way the discussions would go ;) ). From what I can see

Re: [PHP-DEV] Re: [fw-webservices] Re: [PHP-DEV] RFC - "class underloading" -or- "ancestor overloading"

2010-03-15 Thread Larry Garfield
On Monday 15 March 2010 03:08:28 pm Nate Gordon wrote: > > If there were a syntactic-level support for "wrap this object in this > > class and pass through any method that isn't redefined", a sort of > > sideways extends, > > that would become much simpler. I'm not sure what that would look like,

Re: [PHP-DEV] Re: [fw-webservices] Re: [PHP-DEV] RFC - "class underloading" -or- "ancestor overloading"

2010-03-15 Thread Nate Gordon
On Mon, Mar 15, 2010 at 2:14 PM, Larry Garfield wrote: > The challenge of "never use extend" is that simply wrapping classes in > decorators only goes so far. You can't always maintain interface > compliance > if you're nesting decorators, and if you're overriding only one out of a > dozen > or t

Re: [PHP-DEV] Re: [fw-webservices] Re: [PHP-DEV] RFC - "class underloading" -or- "ancestor overloading"

2010-03-15 Thread Larry Garfield
The challenge of "never use extend" is that simply wrapping classes in decorators only goes so far. You can't always maintain interface compliance if you're nesting decorators, and if you're overriding only one out of a dozen or two methods then you have a lot of foo() { return $obj->foo(); } m

Re: [PHP-DEV] Implementing fdopen in PHP

2010-03-15 Thread Arnaud Le Blanc
Le dimanche 14 mars 2010 à 17:38 +1100, Dennis Hotson a écrit : > Hi all, > > It's my first post, so go easy on me. :-) > > I'm trying to implement PHP support for github's erlang RPC server called > ernie. > So basically I've been porting the following ruby code to PHP: > http://github.com/mojom

[PHP-DEV] Re: [fw-webservices] Re: [PHP-DEV] RFC - "class underloading" -or- "ancestor overloading"

2010-03-15 Thread Hector Virgen
I also ran into this problem with Zend_Db_Select. I wanted to add a new constant to improve my usage of Zend_Db_Table#select(), but that method would always returns an instance of Zend_Db_Table_Select which extended Zend_Db_Select. There was no easy way for me to add my class constant without resor

Re: [PHP-DEV] SVN Account Request: ondrej

2010-03-15 Thread Ondřej Surý
Hi Pierre, On Wed, Mar 10, 2010 at 21:45, Pierre Joye wrote: > hi Ondrej, > > Your account can and certainly will be approved once you have provided > a serie of patches and they have been applied (already one in the > queue :). Ok, makes sense. BTW Are you considering to apply that "use intern

Re: [PHP-DEV] Bug # 50755

2010-03-15 Thread Christopher Jones
Stanley Sufficool wrote: > I have attached patches for bug # 50755 on bugs.php.net. These also > cleanup to PDO DBLIB code to have less of a memory footprint and to > prepare for other feature additions such as multiple rowset support. > > I have compiled and tested on x86. > > Can someone revie

Re: [PHP-DEV] Next major version must be 7 (Lessons learned from the ECMAScript committee)

2010-03-15 Thread Stanislav Malyshev
Hi! E (for ergo): The next major version of PHP must be called 7, to avoid confusion. Could we not at least agree on this? Why should we care? When we have that version working, we could have long, nice and pleasant flame^H^H^H^H^Hdiscussion about it. Right now this is one question that we a