commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: [collections] Collections Next Gen
Date Wed, 02 Apr 2003 17:06:13 GMT


>I'd like to standardise this as either something we obey, or don't
>Personally I've never liked it and not obeyed it, as a putAll or addAll
>method easily handles this functionality. Usually the Collections
>has obeyed it however, as it is an unwritten part of the specification
>are obeying. It seems we have three options I think:
>1) We strictly obey the specification. A collection-type parameter to a
>constructor is a copy-by-value.

Same here:  I've never lked it, never obeyed it.  I do like putAll and
addAll.  So I like the above , #1 option in your email, as it's the most
consistent and least confusing.

Yoav Shapira
Millennium ChemInformatics

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

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

View raw message