Hi!
> Please also add html escaping for the entry (some entres contain i.e.
"->")
Done, added it to bin/news2html on phpweb.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscri
Hi internals!
I started the vote on the operator overloading / GMP RFC:
https://wiki.php.net/rfc/operator_overloading_gmp#vote
Thanks,
Nikita
Hi internals!
We just published some rather extensive documentation on internal object
orientation:
http://www.phpinternalsbook.com/classes_objects.html
This is part of a larger project aimed at documenting the engine and making
it accessible to new contributors.
Any feedback is appreciated
Hi Stas,
On Mon, 2013-06-10 at 10:54 -0700, Stas Malyshev wrote:
> Hi!
>
> > Stas, Johannes? We have to fix this crash, in one way or another. The
> > current patch is good imo.
>
> I'm ok with this in 5.4 but I'd really like to fix the var_dump issue if
> possible.
I've reworked the patch bef
Hi!
> Stas, Johannes? We have to fix this crash, in one way or another. The
> current patch is good imo.
I'm ok with this in 5.4 but I'd really like to fix the var_dump issue if
possible.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
P
Hi!
> As I mentioned previously, that small piece is easy fixable, though it
> possibly makes that place not portable between 32 and 64 bit. The main
> intention is to fix the unserialization crash, which IMHO interleaves this
> small deviation.
What you mean by not portable? Different code, diff
On Mon, Jun 10, 2013 at 2:33 PM, Johannes Schlüter
wrote:
> On Mon, 2013-06-10 at 14:07 +0200, Etienne Kneuss wrote:
>
>
>> I propose we fix the serialization/unserialization crash in a way that
>> does not affect var_dump.
>
> That was the summary of my message a while back, too. Aside from that
On Mon, June 10, 2013 14:04, Etienne Kneuss wrote:
> On Mon, Jun 10, 2013 at 1:56 PM, Anatol Belski wrote:
>
>
>> Hi Etienne,
>>
>>
>> On Mon, June 10, 2013 13:24, Etienne Kneuss wrote:
>>
>>> On Fri, Jun 7, 2013 at 9:27 PM, Gustavo Lopes
>>> wrote:
>>>
>>>
>>>
On Fri, 07 Jun 2013 14:06:11 +0
On Mon, 2013-06-10 at 14:07 +0200, Etienne Kneuss wrote:
> I propose we fix the serialization/unserialization crash in a way that
> does not affect var_dump.
That was the summary of my message a while back, too. Aside from that I
trust the assessment of extension maintainers.
I want to take thi
On Mon, Jun 10, 2013 at 1:47 PM, Pierre Joye wrote:
>
> On Jun 10, 2013 1:24 PM, "Etienne Kneuss" wrote:
> >
>
> > So if I understand correctly var_dump now indicates a different type than
> > what accessing the property returns?
> >
> > Even if the change itself does not constitute a big BC bre
On Mon, Jun 10, 2013 at 1:56 PM, Anatol Belski wrote:
> Hi Etienne,
>
> On Mon, June 10, 2013 13:24, Etienne Kneuss wrote:
> > On Fri, Jun 7, 2013 at 9:27 PM, Gustavo Lopes
> > wrote:
> >
> >
> >> On Fri, 07 Jun 2013 14:06:11 +0200, Derick Rethans
> >> wrote:
> >>
> >>
> >> That's the one where
Hi Etienne,
On Mon, June 10, 2013 13:24, Etienne Kneuss wrote:
> On Fri, Jun 7, 2013 at 9:27 PM, Gustavo Lopes
> wrote:
>
>
>> On Fri, 07 Jun 2013 14:06:11 +0200, Derick Rethans
>> wrote:
>>
>>
>> That's the one where conversion int <> string for serialization was
>>
developed. It came into
On Jun 10, 2013 1:24 PM, "Etienne Kneuss" wrote:
>
> So if I understand correctly var_dump now indicates a different type than
> what accessing the property returns?
>
> Even if the change itself does not constitute a big BC break, this
> behavior is confusing and seems like a big no-no to me.
On Fri, Jun 7, 2013 at 9:27 PM, Gustavo Lopes wrote:
> On Fri, 07 Jun 2013 14:06:11 +0200, Derick Rethans wrote:
>
> That's the one where conversion int <> string for serialization was
>>> developed. It came into 5.5 with this patches (the originally proposed
>>> patch is still attached to that
hi,
On Fri, Jun 7, 2013 at 9:27 PM, Gustavo Lopes wrote:
> On Fri, 07 Jun 2013 14:06:11 +0200, Derick Rethans wrote:
>
>>> That's the one where conversion int <> string for serialization was
>>> developed. It came into 5.5 with this patches (the originally proposed
>>> patch is still attached to
Hi Terry,
Sorry for slow response.
I'm very busy with other work and have no time for MLC OPcache review.
I don't think we can include it into main tree before 5.5.0 release anyway.
But in general I think we may include your work in the future releases.
Also, thanks for useful reports about probl
16 matches
Mail list logo
