We could have stages:
- Now: Mark all methods we want as deprecated, which gives us a record of
intention at least.
- 2.0: Drop private and package private deprecated methods
- 2.1: Drop protected and public deprecated methods
Gary Gregory
Senior Software Engineer
Seagull Software
email: ggreg...
There are a lot of classes which have setters for private fields that
are also set by the constructors.
In most cases there is no need to change the values of the fields
after construction, so the setters could be dropped and the fields
made final thus improving thread-safety.
Final fields also ma
It is a very common requirement that some configuration value changes across
environments (dev/qa/stg/prd etc). I went through the documentation but didn't
find any feature to do this in the Configuration (please correct me if you know
a way to do this).
If such feature doesn't already there, I
Gilles Sadowski wrote:
> Hi.
>
> I noticed that when fully-qualified names are used, the text layout
> sometimes becomes fairly ugly (lines of uneven lengths). We could just refer
> to the short name since it should be a link to the corresponding javadoc
> (where the reader can see the package nam
Hello.
The "DimensionMismatchException" is a checked exception although it is used
to signal unfulfilled preconditions. It should really be an unchecked
exception. [It could be turned into a subclass of "MathRuntimeException"
while working on issue MATH-361.]
Best,
Gilles
---
Hi.
I noticed that when fully-qualified names are used, the text layout
sometimes becomes fairly ugly (lines of uneven lengths). We could just refer
to the short name since it should be a link to the corresponding javadoc
(where the reader can see the package name).
Best,
Gilles
---
