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 Jared.Becksfort@stjude.org
 designates 192.55.208.21 as permitted sender)
Message-ID: <8172D639BA76A14AA5C9DE7E13E0CEBE4DBAE81E5E@10.stjude.org>
From: "Becksfort, Jared" <Jared.Becksfort@STJUDE.ORG>
To: Commons Developers List <dev@commons.apache.org>
Date: Wed, 1 Aug 2012 12:09:15 -0500
Subject: RE: My vote for release
Thread-Topic: My vote for release
Thread-Index: Ac1wB7eU0yw22vQ1TjWLYubDIM2KJQAAEHfg
References: <19d96013-8a0a-4199-af8a-5149686213c6@sonalysts.com>
	<CAJm2B-mpbTBgkjOtTRvCx8CiWAU8a9ahc5cT2_rw0kbgm0HOiA@mail.gmail.com>
 <d132170f-2baa-4788-9b4b-4d215a22b4dd@sonalysts.com>
In-Reply-To: <d132170f-2baa-4788-9b4b-4d215a22b4dd@sonalysts.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-SEF-7853D99-ADF1-478E-8894-213D316B8FFA: 1
X-V-Loop: Yes

Gary,

I have wondered about the public scoping of arrays myself for that same rea=
son.  I also write image processing code, and the arrays can be quite large=
, especially if the processing is in three dimensions.

Jared

-----Original Message-----
From: Gary Lucas [mailto:gwlucas@sonalysts.com]
Sent: Wednesday, August 01, 2012 12:01 PM
To: 'Commons Developers List'
Subject: My vote for release


Damjan,

I just saw that you were soliciting votes for release.   I think you've don=
e an outstanding job and I'm all for it.   I would vote twice if I could :-=
)

I saw that some of the folks on the Apache page were complaining about some=
 of the code-checking issues. I've never looked at these myself, but I supp=
ose that many of them are not worth fixing.

For example, somebody complained that a class shouldn't have a publically s=
coped array.  Let's say a programmer tried to address that.  If he writes a=
 "get" method that is a simple pass-through returning a reference to the in=
ternal array, has he really added any security (meaning protection against =
accidental misuse)?  Of course not.  Suppose, instead, that he writes a met=
hod that makes a copy of the array before returning it.  Now he's improved =
security, but degraded the performance of the overall code... maybe serious=
ly. And in imaging processing, performance trumps security almost every tim=
e.

Anyway, if there are specific areas in the TIFF tree or elsewhere that you =
would like me to review, please let me know and I'll be glad to take a look=
 at them.

Gary


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


Email Disclaimer:  www.stjude.org/emaildisclaimer
Consultation Disclaimer:  www.stjude.org/consultationdisclaimer


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