2009/8/7 Andre Hübner
> http://bugs.php.net/bug.php?id=48880 is reason enough to want a
>>> release soon - PHP 5.3 died a very fast death in production here.
>>>
>>
> for me too. this bug makes 5.3.0 unusable for me. svn is not an option for
> production environment.
>
> Thanks,
> Andre
>
>
>
Y
2009/7/30 David Coallier
> >
> > What do you think about the possibility to support ArrayObject
> > instances in array_* functions?
> > If you all agreed on this, I can definately help to complete the
> > patch, but I need some initial guidance to finish at least the first
> > function.
> >
>
> I
2009/7/10 Alain Williams
> On Fri, Jul 10, 2009 at 01:35:45PM +0300, Ionut G. Stan wrote:
> > On 7/10/2009 13:23, Giovanni Giacobbi wrote:
> > >On Fri, Jul 10, 2009 at 02:44:52AM +0200, troels knak-nielsen wrote:
> > >[...]
> > >
> > >>For example, instead of:
> > >>
> > >> function addFive(i
2009/7/10 Ionut G. Stan
> On 7/10/2009 13:23, Giovanni Giacobbi wrote:
>
>> On Fri, Jul 10, 2009 at 02:44:52AM +0200, troels knak-nielsen wrote:
>> [...]
>>
>>
>>> For example, instead of:
>>>
>>> function addFive(int $x) {
>>> return $x + 5;
>>> }
>>>
>>> You would simply do:
>>>
>
2009/7/2 Paul Biggar
> On Thu, Jul 2, 2009 at 3:17 PM, Jonathan Bond-Caron
> wrote:
> > From userland, I'm a big fan of this proposal / agree to the principle
> although I'm not convinced that
> >
> > function($quantity)
> > function(int $quantity)
> > function(+int $quantity)
> > function(-int $
Regarding ifsetor, what's wrong with just using this:
isset($myvar) OR $myvar = 'i am set';
It works in just the same way and has no problems. I agree it would be
great though if there could be a function to retrieve a variable's
value if it exists, without throwing an error if it doesn't exist.
Why not allow a class prefix as an option to the function?
Eg:
'php-highlighted-' as the prefix would produce things like
'php-highlighted-keyword'.
That way there's no risk of collision and there's no need to
over-complicated things.
2009/4/2 Robert Cummings :
> On Thu, 2009-04-02 at 09:13 -07
Exactly. In javascript terms, that is what you'd expect since:
array(1=>'test')
..Isn't a valid array.
2009/3/17 Scott MacVicar :
> On 11 Mar 2009, at 19:25, Christopher Östlund wrote:
>
>> I think this behavior is a bit odd too:
>>
>> php -r "echo json_encode(array(0=>'test'));" // ["test"]
>>
I think what you're doing is effectively the same as doing:
$fb = new Part .''. SubPart();
So basically concatenating a new instance of Part, with the results
from the function SubPart. Try defining Part as a class and see what
error you get. If I'm right, you'll get an undefined function error.
