On 12 Aug 2010, at 16:04, Johannes Schlüter wrote:
> While discussing this via IRC it was suggested to create an
> "Experimental" top-level category on pecl.php.net and put them there. To
> me this looks like a good proposal. From there they can easily be picked
> up, be extended, provide ideas f
On 11 Aug 2010, at 17:01, Elizabeth M Smith wrote:
> Well this is turning into a real flamefest.
I'm now totally confused to be honest.
> Personally I really HATE the 5.3 implementation of "typehints" - heck you
> can't even typehint arrays with an arrayobject instance, it's not hinting in
>
On 11 Aug 2010, at 15:13, Zeev Suraski wrote:
> Maybe I'm old school, but in my opinion, trunk should only contain
> agreed-upon features. It should also always build and pass tests
> successfully. It's not the wild-west version of PHP, it's PHP's next
> version, in progress. Want to work o
On 17 Jun 2010, at 20:14, Stas Malyshev wrote:
> Hi!
>
>> I know the discussion is about scalar type hints. But what is with a
>> object type hint as base for all objects?
>
> When it makes sense to accept any object, regardless of the class, but not
> other types? I wonder if it's really a c
In my example static const did have internal linkage, const on its own in the
global scope did not. You still need static.
Melanie
On 14 Jun 2010, at 12:28, Gustavo Lopes wrote:
> On Mon, 14 Jun 2010 11:56:57 +0100, Melanie Rhianna Lewis
> wrote:
>
>> My feeling is that they
My feeling is that they should all be static consts unless explicitly accessed
outside of the object module or changed.Since typically they're a list of
function/method entries only accessed by a class or zend_module_entry that is
really the case. Without the static we're polluting the name
