Jody Garnett ha scritto: > Good discussion Andrea, I am sorry I cannot give this my full attention.
>> 2) iterating over values of the collection is something that will >> no to throw exceptions, unless I'm doing something like parallel >> modifications > This is the crux of the matter is it not? > ConcurrentModificationException is not document as an explicit > restriction (it is just something implementations can restrict if they > want), as such it only shows up as a RuntimeException and is not part of > the signature. This is something only produced by a "fail fast > iterator".... and only as a result of the provided implementations not > being thread safe. From the ConcurrentModificationException javadoc: "Therefore, it would be wrong to write a program that depended on this exception for its correctness: ConcurrentModificationException should be used only to detect bugs." See? Collections do throw exceptions _only_ when your program misuses them. Our FeatureCollection throws exception because someone pulled the network plug or because we don't have rights to write on disk. It's not the same thing. Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
