Re: Is this a violation of the EOF commandment?
Re: Is this a violation of the EOF commandment?
- Subject: Re: Is this a violation of the EOF commandment?
- From: Denis Frolov <email@hidden>
- Date: Fri, 13 Nov 2009 09:28:33 +0300
Although this doesn't violate EOF commandments, I think it does
violate Principle of least astonishment. Here is a discussion of this
question on stackoverflow -
http://stackoverflow.com/questions/433678/modifying-setter-argument-is-it-hack-or-not
Personally, I'm with with the answer by Bill the Lizard although most
of the votes went to the opposite one (i.e. "it's ok to do that").
On Fri, Nov 13, 2009 at 12:49 AM, Ricardo J. Parada <email@hidden> wrote:
>
> public void setCpt(String value) {
> if (value != null) value = value.toUpperCase();
> super.setCpt(value);
> }
> P.S. I'm using eo-gap generation pattern. So this class extends the _ class
> generated by the _WonderEntity.java template.
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden