Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of
 SRS0=Qplp=AT=m4x.org=sebastien.brisard@bounces.m4x.org designates
 129.104.30.34 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F339572.8050509@free.fr>
References: 
 <CAGRH7HpAMfT6mCdwm0CCKzm+rQBNcVyipx43xz-a-h=Tmdck7g@mail.gmail.com>
	<4F339572.8050509@free.fr>
Date: Thu, 9 Feb 2012 10:50:09 +0100
Message-ID: 
 <CAGRH7Hqe-N7sHr_wz4FB5FxOtadfhEu2tWbE-PNY-6Jvf9oGiw@mail.gmail.com>
Subject: Re: [math] Package transform revisited
From: =?ISO-8859-1?Q?S=E9bastien_Brisard?= <sebastien.brisard@m4x.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Luc,
>
> I agree with you, enums are much better. There are other places in
> [math] where we use boolean or even ints for such things. They mainly
> came for pre-java 5 era when enums where not available.
>
> Luc
>
And what do you think of replacing
- transform(double[]) with transform(double[], FORWARD)
- inverseTransform(double[]) with transform(double[], INVERSE)
(also using enums) ?
In fact, at the lowest level, all transforms are coded this way (a
boolean is passed to specifiy whether or not the inverse is to be
computed). So maybe the higher level methods should also do so.
S=E9bastien


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org