Stanislav Malyshev wrote on 23/03/2015 05:21:
Hi!
Looking into some issue, I've discovered that, to my surprise,
Exceptions are serializable. Except that it doesn't always work of
course (e.g. see http://stackoverflow.com/q/9747813/214196) because
exceptions contain backtraces, and those can
-Ursprüngliche Nachricht-
Von: Pierre Joye [mailto:pierre@gmail.com]
Gesendet: Montag, 23. März 2015 06:57
An: Juan Basso
Cc: Stanislav Malyshev; PHP Internals
Betreff: Re: [PHP-DEV] Serializing exceptions
On Mon, Mar 23, 2015 at 12:31 PM, Juan Basso jrba...@gmail.com wrote:
Hi,
Am 23.03.2015 um 06:21 schrieb Stanislav Malyshev:
Looking into some issue, I've discovered that, to my surprise,
Exceptions are serializable. Except that it doesn't always work of
course (e.g. see http://stackoverflow.com/q/9747813/214196) because
exceptions contain backtraces, and those
On Mar 21, 2015, at 9:05 AM, Rasmus Lerdorf ras...@lerdorf.com wrote:
On 03/21/2015 08:52 AM, François Laupretre wrote:
Now, after more calls from many of you to delay it, and as Zeev himself
seemed to consider it as more acceptable, I am proposing again to delay 7.0
feature freeze to May,
Hey:
On Tue, Mar 24, 2015 at 1:31 PM, Pierre Joye pierre@gmail.com wrote:
hi!
On Tue, Mar 24, 2015 at 5:41 AM, Dmitry Stogov dmi...@zend.com wrote:
Hi,
Recently, Xinchen and me worked on optimization that eliminates useless
reallocations and copying during string concatenation
hi!
On Tue, Mar 24, 2015 at 5:41 AM, Dmitry Stogov dmi...@zend.com wrote:
Hi,
Recently, Xinchen and me worked on optimization that eliminates useless
reallocations and copying during string concatenation (ZEND_ADD_STRING and
family + ZEND_CONCAT).
The idea comes from ropes, but adopted
On Tue, Mar 24, 2015 at 12:35 PM, Xinchen Hui xinche...@zend.com wrote:
Hey:
On Tue, Mar 24, 2015 at 1:31 PM, Pierre Joye pierre@gmail.com wrote:
hi!
On Tue, Mar 24, 2015 at 5:41 AM, Dmitry Stogov dmi...@zend.com wrote:
Hi,
Recently, Xinchen and me worked on optimization that
Hi!
This makes an opportunity to replace the old API with object oriented one
preventing any kind of BC break.
But instead of using this as an extension because of some limitations
like
“string”-startsWith(‘s’); the API should be bundled with the engine (not
written in PHP).
This
Hi!
famous articles written about it like PHP fractal of bad design and
That article. Which is from what I remember last time reading it was
about 75% like why I need to look in the manual instead of language
being magically exactly the way I imagine it should be without any
basis?. And another
Hi!
Maybe you can implement the __sleep method and just return the
documented attributes (message, code, file, line).
That would be an option, but before going there, my question is - does
anybody need it, really?
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime
Hi!
I think we should discuss if (un)serialization is a first-class
operation in the language and if so, we should try to make everything
serializable. Currently, we introduce more and more unserializable
I don't think we can, not unless we can serialize PHP code (like Java
can have JARs with
From: Stanislav Malyshev [mailto:smalys...@gmail.com], Sent: Monday, March 23,
2015 7:45 AM
Hi!
Maybe you can implement the __sleep method and just return the
documented attributes (message, code, file, line).
That would be an option, but before going there, my question is - does
anybody
i didn't mention any break or things. also many languages are different
Yes you did. You just proposed removing large part of PHP API. That
would break things, there can be no confusion about it.
I just agree with you. we shouldn't :) the old API will stay no one
will ever remove it.
Hi,
Recently, Xinchen and me worked on optimization that eliminates useless
reallocations and copying during string concatenation (ZEND_ADD_STRING and
family + ZEND_CONCAT).
The idea comes from ropes, but adopted especially for our needs.
Rope is popular data structure in languages with
14 matches
Mail list logo
