I agree 100%
-Chris
On Aug 15, 2009, at 9:50 AM, Ian Robertson <ian...@gm...>
wrote:
> Currently, pojomatic allows static fields and methods to be
> annotated with @Property. While there is nothing technically wrong
> with this, it seems highly likely to be a programmer error. Indeed,
> it makes no sense to include a static in equals, and can only serve
> to break hashCode by allowing instances to have their hashCode
> change after insertion into a (key)set. At best, it could possibly
> make sense in a toString implementation, though I can think of no
> reasonable use case for that.
>
> I think we should throw an IllegalArgumentException at PojomatorImpl
> construction time if a static is so annotated. Thoughts?
>
> - Ian
> ---
> ---
> ---
> ---------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day
> trial. Simplify your report design, integration and deployment - and
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Pojomatic-users mailing list
> Poj...@li...
> https://lists.sourceforge.net/lists/listinfo/pojomatic-users
|
