commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Becksfort, Jared" <Jared.Becksf...@STJUDE.ORG>
Subject RE: My vote for release
Date Wed, 01 Aug 2012 17:09:15 GMT

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


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


I just saw that you were soliciting votes for release.   I think you've done 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 suppose that many of them are not worth fixing.

For example, somebody complained that a class shouldn't have a publically scoped 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 internal array, has he really added any security (meaning protection
against accidental misuse)?  Of course not.  Suppose, instead, that he writes a method that
makes a copy of the array before returning it.  Now he's improved security, but degraded the
performance of the overall code... maybe seriously. And in imaging processing, performance
trumps security almost every time.

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.


To unsubscribe, e-mail:
For additional commands, e-mail:

Email Disclaimer:
Consultation Disclaimer:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message