|
From: Colin S. <col...@ex...> - 2004-10-21 12:33:58
|
I personally don't get that hung up about it. Both or equally valid forms (and recognized by JavaBeans tools and the like), and the reality is that sometimes you have a word which sounds horrible with is and ok with get, or vice-versa. On the other hand, if they sound ok both ways then there's nothing wrong with trying to be consistent. jürgen höller [werk3AT] wrote: >I've just noticed that we're slightly inconsistent in our naming for getters that return boolean bean properties. Most of them are called "isXxx", but 9 of them in the entire codebase are called "getXxx". > >We should find a consistent rule here. For example, should we prefer "isProxyTargetClass" or "getProxyTargetClass"? Neither is nice English, so I guess it's more about a convention then about nice method names. > >I tend to prefer the "isXxx" versions for all boolean properties. That would also be easier in terms of affected classes, as we just have 9 accessors that do not conform to that rule (i.e. 9 to be deprecated). > >On the other hand, "getXxx" might result in slightly nicer English in some boolean cases... > >Opinions? > >Juergen > > |