Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.albasani.net!.POSTED!not-for-mail From: Jan Burse Newsgroups: comp.lang.java.programmer Subject: Re: Fixing "typos" in enums... Date: Sat, 16 Nov 2013 10:16:07 +0100 Organization: albasani.net Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net NU45O2fM2JkoErE5n0CArlVchHG+cnZl5HEuoM8MG2uIBhAITd9bCA2oib5se1Jo6QGguFqt3LDc1HDTNYPd/A== NNTP-Posting-Date: Sat, 16 Nov 2013 09:16:08 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="hX9h6hjekQAPqCpHUt+mt/gHVyXDvjVObblTsv+PnvGRDgk6Pzt3/D8ZB0RxLa2IaK7m06INdEbsMxmG3zLlqkmMrpEgzLonj5wU4/wQPNd3KHwoJMiEJ1cDBuqvT47K"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0 SeaMonkey/2.22 In-Reply-To: Cancel-Lock: sha1:gfS+1+0q5PYQ0NSHPSnPugMkQmU= Xref: csiph.com comp.lang.java.programmer:26517 Andreas Leitgeb schrieb: > // public enum Foo { FURST, SECOND } > public enum Foo { FIRST, SECOND; public static final FURST = FIRST; } Maybe mark FURST also as deprecated. And put a comment that says what should be used instead of FURST, which could go into javadoc. And of course replacing FURST by FIRST shouldn't be an issue when your project and the clients of your project are in the reach of refactoring tools. But yes for public APIs, this is annoying. In as far APIs behave similar as natural language since for whatever reason synonyms develop, and even word meanings disappear over the time. Overloading of methods even allows a form of polysemy. Bye