Hi!
> -1 on this. If there is no technical problem with serializing the
> Exception class itself, it should be possible to serialize it. It can
> always happen that an object contains some not-serializable member, this
> is nothing specific to exceptions. I don't see the point of this change.
The point is exactly that Exception contains non-serializable members
that makes successfully serializing and restoring them impossible. You
could get back something that looks like an Exception, but not the
original one - namely, you can not store and restore backtraces.
> Also, Christian Stoller's mail pointed out that Symfony uses serialized
> exceptions.
I must have missed it - what Symphony uses serialized exceptions for?
--
Stas Malyshev
[email protected]