On 22/01/2009, Niall Pemberton wrote:
> On Wed, Jan 21, 2009 at 11:16 AM, Phil Steitz wrote:
> > sebb wrote:
> >>
> >> On 20/01/2009, Phil Steitz wrote:
> >>
> >>>
> >>> I would like to ask that these changes be reverted. Deprecated classes
> >>> and
> >>> client code breakage that dep
On Wed, Jan 21, 2009 at 11:16 AM, Phil Steitz wrote:
> sebb wrote:
>>
>> On 20/01/2009, Phil Steitz wrote:
>>
>>>
>>> I would like to ask that these changes be reverted. Deprecated classes
>>> and
>>> client code breakage that depends on them can only happen in major (x.0)
>>> releases. Unless
Phil Steitz wrote:
> sebb wrote:
>> On 20/01/2009, Phil Steitz wrote:
>>
>>> I would like to ask that these changes be reverted. Deprecated
>>> classes and
>>> client code breakage that depends on them can only happen in major (x.0)
>>> releases. Unless I am missing something subtle, these ch
sebb wrote:
On 20/01/2009, Phil Steitz wrote:
I would like to ask that these changes be reverted. Deprecated classes and
client code breakage that depends on them can only happen in major (x.0)
releases. Unless I am missing something subtle, these changes will break
client code that speci
On 20/01/2009, Phil Steitz wrote:
> I would like to ask that these changes be reverted. Deprecated classes and
> client code breakage that depends on them can only happen in major (x.0)
> releases. Unless I am missing something subtle, these changes will break
> client code that specializes the
I would like to ask that these changes be reverted. Deprecated classes
and client code breakage that depends on them can only happen in major
(x.0) releases. Unless I am missing something subtle, these changes
will break client code that specializes the cast on caught exceptions
and tries to
