Hi!
> Also, AFAIR, call_user_func() doesn't work with functions using references
> in args.
Use call_user_func_array() for that, it supports refs.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Development Ma
Johannes,
I completely agree about the E_ERROR - in general. An error should be
recoverable as much as possible. In this concrete case as I've reworking a
patch descending from 2010 and that E_ERROR was there, I just let it go.
The situation is that doing an E_WARNING possibly leaves user with an
Hi,
commit f8b91d9ac (fix for #62852) looks fine to me.
Commit 0ee71 for #53437 is a bit too much for 5.3 in my opinion - what happens
if users have custom work-arounds in extended classes with custom __wakeup or
__set_State methods? Will there be a change of behavihor? I think there should
b
On Mon, 18 Mar 2013 19:03:41 +0400, Julien Pauli wrote:
On Mon, Mar 18, 2013 at 3:33 PM, Anthony Ferrara
wrote:
Angel,
On 18/03/13 14:04, Julien Pauli wrote:
> Also, AFAIR, call_user_func() doesn't work with functions using
> references in args. Julien.Pauli
AFAIK it does.
Do you have an
On Mon, Mar 18, 2013 at 3:33 PM, Anthony Ferrara wrote:
> Angel,
>
> On 18/03/13 14:04, Julien Pauli wrote:
>> > Also, AFAIR, call_user_func() doesn't work with functions using
>> > references in args. Julien.Pauli
>> AFAIK it does.
>> Do you have an example where it doesn't?
>>
>
> It definitely
> Angel,
>
> On 18/03/13 14:04, Julien Pauli wrote:
> > > Also, AFAIR, call_user_func() doesn't work with functions using
> > > references in args. Julien.Pauli
> > AFAIK it does.
> > Do you have an example where it doesn't?
> >
>
> It definitely does not:
>
> http://3v4l.org/C8Kme
>
> And if
Angel,
On 18/03/13 14:04, Julien Pauli wrote:
> > Also, AFAIR, call_user_func() doesn't work with functions using
> > references in args. Julien.Pauli
> AFAIK it does.
> Do you have an example where it doesn't?
>
It definitely does not:
http://3v4l.org/C8Kme
And if you try call-time-pass-by-ref
On 18/03/13 14:04, Julien Pauli wrote:
> Also, AFAIR, call_user_func() doesn't work with functions using
> references in args. Julien.Pauli
AFAIK it does.
Do you have an example where it doesn't?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/u
On Mar 18, 2013, at 5:57 AM, Florian Anderiasch wrote:
> On 03/17/2013 02:12 PM, Clint Priest wrote:
>> Unfortunately my experience with that process has been that many people
>> will vote who had no part in the discussion.
>
> I don't see a point repeating points of discussion when being in
> ag
On Sat, Mar 16, 2013 at 7:51 AM, Sara Golemon wrote:
> > ${'_'.!$_=getCallback()}();
> >
> Well now, that's an... interesting abuse of resolution order and type
> juggling.
>
>
Really crazy, yeah
Also, AFAIR, call_user_func() doesn't work with functions using references
in args.
Julien.Pauli
On 1 Dec 2012, at 12:34, Sebastian Krebs wrote:
> Hi,
>
> Don't want to start a big discussion, but is there a concrete reason, why
> abstract properties (or "a kind of abstract") are not supported?
Hi,
The reason for not having abstract properties is that when you are defining a
type you don'
On 03/17/2013 02:12 PM, Clint Priest wrote:
> Unfortunately my experience with that process has been that many people
> will vote who had no part in the discussion.
I don't see a point repeating points of discussion when being in
agreement with people who already stated their opinion, or being
per
Hi,
#62852 and #53437 introduced fixes for the date extension crashing when
unserializing objects. They was applied to 5.5. If there are no
objections, I would backport those to 5.3 and 5.4.
Regards
Anatol
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://ww
On 18/03/2013, at 6:07 PM, Matīss Roberts Treinis wrote:
> Not only that. This potentially might break compatibility with many
> software products already out there. Also, this might lead to many
> misunderstandings and, in fact, ambiguous code. Consider the sample.
>
> $name = 'something';
> $s
Not only that. This potentially might break compatibility with many
software products already out there. Also, this might lead to many
misunderstandings and, in fact, ambiguous code. Consider the sample.
$name = 'something';
$something = $name(); // What is this - a function call or object?
Fact
15 matches
Mail list logo