Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeder.erje.net!newsfeed.utanet.at!newscore.univie.ac.at!aconews-feed.univie.ac.at!aconews.univie.ac.at!not-for-mail Newsgroups: comp.lang.java.programmer From: Andreas Leitgeb Subject: Re: setSize ArrayList, when will it come? References: <9aetckFmvmU1@mid.individual.net> Reply-To: avl@logic.at User-Agent: slrn/pre0.9.9-111 (Linux) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: Date: 10 Aug 2011 09:14:19 GMT Lines: 15 NNTP-Posting-Host: gamma.logic.tuwien.ac.at X-Trace: 1312967659 tunews.univie.ac.at 71616 128.130.175.3 X-Complaints-To: abuse@tuwien.ac.at Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:6963 Robert Klemme wrote: > On 09.08.2011 04:16, Jan Burse wrote: >> The software refactoring use case, is replacing a synchronized >> Vector by an unsychronized ArrayList in regions where no synchronization >> is necessary. > This can be done in many cases, especially in all cases where Vector > instances are used through the List interface. Originally, Vector wasn't a List. So, really old code isn't very "likely" to use the List interface of Vector. >> Which is eventually abuse of the term "sparse", > If you really need a sparse type ... didn't seem so.