The method comes from a request by me, and isInvalid seems a bit double-negativy to me. If it returns false, it's not invalid, which means not not valid, which means valid. From a language perspective, it seems clearer to ask if it's valid, and not have a false value negate a negative (even if that means we're asking for an unstable property...I made the point on the MLVM list that Java beans generally don't have isNotSomething-style properties, even though those properties are usually non-volatile/unstable.
That said, I have no strong preference. I just want to be able to query it :) - Charlie On Thu, May 26, 2011 at 2:17 PM, John Rose <[email protected]> wrote: > Invalidity is stable because it is permanent. > > -- John (on my iPhone) > > On May 26, 2011, at 12:10 PM, "Y. S. Ramakrishna" > <[email protected]> wrote: > >> John, you state that validity is not a stable property. >> Is invalidity a stable property, or not even that is. >> > _______________________________________________ > mlvm-dev mailing list > [email protected] > http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev > _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
