Bill Barker wrote:
----- Original Message ----- From: "Ted Dunning" <ted.dunn...@gmail.com>
To: "Commons Developers List" <dev@commons.apache.org>
Sent: Monday, May 25, 2009 4:52 PM
Subject: Re: [math] Serialization
This sounds like the germ of a repair process.
Nuke all Serializable declarations without test cases. Then, add
them back
where people care enough to guarantee correctness by demonstrating a
correct
round trip.
Would get my +1, but for the moment stats.** is such a mess (UID
inherited from an abstract base class 3-4 levels up) that I'd like a
consensus before putting hours into fixing it.
+1 to fix. I was +1 in the early days when things were "overserialized"
(IMO) [1] and am +1 today.
[1] http://markmail.org/thread/ui47gz75ol5euxj4
Phil
On Mon, May 25, 2009 at 4:32 PM, Bill Barker
<billwbar...@verizon.net>wrote:
But again, want to ask advice before going terminator on those
packages.
IMHO, we'll need to write junit tests for the ones that we leave
Serializable, since I already found (and fixed) two classes in
linear that
couldn't be de-serialized.
--
Ted Dunning, CTO
DeepDyve
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
