Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Eric Sosman Newsgroups: comp.lang.java.programmer Subject: Re: Fixing "typos" in enums... Date: Mon, 18 Nov 2013 17:00:56 -0500 Organization: A noiseless patient Spider Lines: 48 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 18 Nov 2013 22:00:56 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="858a9d65d95f4ea4d355bd116aa2cdbf"; logging-data="30378"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/tdpFvMP1GYX/zKFwakJIq" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 In-Reply-To: Cancel-Lock: sha1:KfYpqe4TQWuO8pfs11IfizSvFok= Xref: csiph.com comp.lang.java.programmer:26549 On 11/18/2013 3:09 PM, Andreas Leitgeb wrote: > Eric Sosman wrote: >> On 11/18/2013 1:25 PM, Andreas Leitgeb wrote: >>> It would be nice, if enum had the concept of synonyms: >>> >>> - each synonym is an alias for a particular constant >>> - synonyms would be recognized by valueOf(String) >>> - synonyms could be annotated as @Deprecated >>> - synonyms could be used in a switch, but then the >>> canonical name (or any other synonym for the same >>> constant) must not be used in the same switch. >>> >>> Well, I know it's not going to happen. Just wanted it off my chest ;-) >> It'd make a mess of EnumMaps, too ... > > Nope, don't see what you mean here. The synonyms wouldn't be > separate extra instances, of course, so by the time I'm holding > an instance, its .name() is the canonical one. > Also, if "C" is a canonical constant of enum Foo, and "S" a > synonym of "C" in Foo, then (Foo.S==Foo.C) would be true. Sorry; I didn't pay close enough attention to the details of your dream. :) Still, you've got to admit it might be a wee bit confusing if you did theMap.clear(); assert theMap.size() == 0; // Okay, it's empty. theMap.put(Foo.C, "FIRST"); assert theMap.size() == 1; // Okay, one mapping. theMap.put(Foo.S, "FURST"); assert theMap.size() == 2; // Why does this fail??? >> 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. > > Nice parable :) Yep, there's some material analysis ahead. Perhaps a trifle over-poetic, but there's serious intent. There'll be some amount of pain no matter which route you take, and you're better able to assess it than any of us is. -- Eric Sosman esosman@comcast-dot-net.invalid