Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.datemas.de!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Fixing "typos" in enums... Date: Mon, 18 Nov 2013 20:20:42 +0100 Lines: 20 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net o0Qr/KvfQcVJNKQ5E2NPrwFRYM+M75PBz1CagFoPnDBt6h9gM= Cancel-Lock: sha1:GahDbr65p3Gngi0sWEsnu5nhtDI= User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 In-Reply-To: X-Antivirus: avast! (VPS 131116-1, 16.11.2013), Outbound message X-Antivirus-Status: Clean Xref: csiph.com comp.lang.java.programmer:26544 On 18.11.2013 19:45, Eric Sosman wrote: > I don't think there's any single Right Way to address your > problem, no one-size-fits-all solution. Elsethread it's written > that a published API is "set in stone," but there are many kinds > of stone. Of all posters to this thread, only you know whether > the stone is obsidian or talc; only you know how hard a tool is > required to scratch it. I like that analogy with the different kinds of stone. That fits really well here. Cheers robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/