ISTR someone saying it seemed like it would be safe to make this break in
BC because there were likely to be no existing FastDateParser subclasses.
However, the compatibility was preserved in FastDateFormat by passing
through a null *to* FastDateParser, so doing the same on FastDateParser
itself wo
Can we add back a ctor?
Gary
On Thu, Feb 27, 2014 at 10:37 AM, Benedikt Ritter wrote:
> Hi,
>
> I'm preparing lang 3.3 RC 1. While looking through the reports I've
> noticed, that we have a Clirr error in 3.3 compared to 3.2.1 [1]. This was
> introduced in r1557882 [2]. The change is a result o
Hi,
I'm preparing lang 3.3 RC 1. While looking through the reports I've
noticed, that we have a Clirr error in 3.3 compared to 3.2.1 [1]. This was
introduced in r1557882 [2]. The change is a result of LANG-950 [3]
The question for me is: can we handle this change without breaking BC?
Benedikt
[
