[DISCUSS] Deprecation in 1.3

[Frank Bille <fr...@gmail.com>]

I think that we have some places in 1.3 where we shouldn't deprecate the
API. This is areas where the deprecation says "Will be removed/moved in 2.0".
I think it is a bit annoying to develop an application and suddenly find
that I can't get rid of some deprecation warnings because there is no
alternative. If I use 1.3 I don't care if EnumeratedType will be replaced
with 1.5 enums in 2.0. Tha'ts nice to know but not a reason to deprecate
IMHO.

ATM I have come across two places which I think should have removed there
deprecation tag all together:

- IExceptionSettings and children
- EnumeratedType

WDYT?

Frank

Re: [DISCUSS] Deprecation in 1.3

[Eelco Hillenius <ee...@gmail.com>]

Agreed. Go ahead. Mostly me put them in there anyway.

Eelco


On 3/6/07, Frank Bille <fr...@gmail.com> wrote:
> I think that we have some places in 1.3 where we shouldn't deprecate the
> API. This is areas where the deprecation says "Will be removed/moved in 2.0".
> I think it is a bit annoying to develop an application and suddenly find
> that I can't get rid of some deprecation warnings because there is no
> alternative. If I use 1.3 I don't care if EnumeratedType will be replaced
> with 1.5 enums in 2.0. Tha'ts nice to know but not a reason to deprecate
> IMHO.
>
> ATM I have come across two places which I think should have removed there
> deprecation tag all together:
>
> - IExceptionSettings and children
> - EnumeratedType
>
> WDYT?
>
> Frank
>