Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: Why "lock" functionality is introduced for all the objects? Date: Tue, 28 Jun 2011 20:43:57 -0400 Organization: A noiseless patient Spider Lines: 12 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Wed, 29 Jun 2011 00:44:19 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="BrOwaJANne849xlH+KPYjQ"; logging-data="6637"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/boub91ZnSHOP8AyKYYccP" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 In-Reply-To: Cancel-Lock: sha1:oAox7QPKNbWigxa7LUKvb040efU= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5756 On 6/28/2011 4:43 PM, BGB wrote: > [...] > they made every object lockable but not every object cloneable, where > one would think cloning would be generally a higher priority. class MySingleton implements Cloneable { // What's wrong with this picture? } -- Eric Sosman esosman@ieee-dot-org.invalid