Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: Jan Burse Newsgroups: comp.lang.java.programmer Subject: Re: BitSet vs BigInteger (false Android doc) Date: Tue, 06 Sep 2011 12:12:38 +0200 Organization: albasani.net Lines: 28 Message-ID: References: <4e613b65$0$311$14726298@news.sunsite.dk> <_ZGdna1ucfWYH__TnZ2dnUVZ_oudnZ2d@earthlink.com> <4e655c24$0$308$14726298@news.sunsite.dk> <826a6f26-c540-4ee9-a0c6-1cf77f20d765@glegroupsg2000goo.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net LG+ufO+kN/J6uPfG8dpHfMH+JqmQ4z08mrX3fO07Ki+LhTqTJyLGLBXpNWRKfceLncbiCflvcxQvAXL1IluIhA== NNTP-Posting-Date: Tue, 6 Sep 2011 10:12:38 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="6GbBQONHWUgbHyUWomIkFMlhKzquKYAm7IYpneMdze1E8XXI7CaNu6wQKBuq2c/WVu0nADVPRrtReqbdyNeOD3ZGCpkcWzSpKRUrN6DWL0oMXVmY/OYVPyn7i/qRWP2/"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.1) Gecko/20110830 Firefox/6.0.1 SeaMonkey/2.3.1 In-Reply-To: Cancel-Lock: sha1:obGmE5sQ6pKZ6zWMO9tj/GUsyy4= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:7618 Jan Burse schrieb: > ut what concerns the Android comment. It is false because > two's complement is not relevant when we compare BitSet and > BigInteger, because two's complement is one way to represent > a negative number: > > ...1xxxxxxx Lew wrote: > The concepts of sign-magnitude, 1s- or 2s-complement, sign, sign > extension, and negative and positive values are all > equally meaningless and completely irrelevant for BitSet. At least here you agree that the Android java doc comment is flawed. But then somehow your abandon your own observations in favor of the "obvious": Lew also wrote: > Are you referring to Android's documentation for BigInteger, which > states, "This API includes operations for bitwise operations in two's > complement [sic] representation. Two's complement is not the internal > representation used by this implementation, so such methods may be > inefficient. Use _BitSet_ for high-performance bitwise operations on > arbitrarily-large sequences of bits."? > > How is that false? It's obviously factual and correct. Bye