Anton, thank you for pointing out to awt/swing classes - I've looked through a number of randomly selected classes and I've realized that many of them haven't specified serial form.
I'll try to estimate percentage of such classes. Thanks, Stepan. On 5/2/06, Anton Avtamonov wrote:
Stepan. Let me answer you shortly: yes, my main concern is about an assetion step. Just because I saw too many classes without specified serialization form, without equals() and so on. Actually, I suppose that is the entire graphical framework (awt + Swing) which is definitely more then 5% :-). I didn't deep investigations of course, but suppose that the simple assertion approach would not work there. Just because it will require to compare specific fields rather than call assertEquals(). About third scenario with IOException. If IOException is the only possible reaction for incorrect form then you are right: we don't need any specific checks. -- Anton Avtamonov, Intel Middleware Products Division <SNIP>
-- Thanks, Stepan Mishura Intel Middleware Products Division ------------------------------------------------------ Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
