Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "OJB Developers List" <ojb-dev@db.apache.org>
Received-SPF: neutral (hermes.apache.org: local policy)
Message-ID: <425F7299.90303@apache.org>
Date: Fri, 15 Apr 2005 09:51:53 +0200
From: =?ISO-8859-1?Q?Martin_Kal=E9n?= <mkalen@apache.org>
Organization: ASF
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: OJB Developers List <ojb-dev@db.apache.org>
Subject: Re: [rfc] Do we need a naming standard ?
References: <316E5B943771D311BAC500805FD7A0780260B907@MAIL.osn.state.oh.us>
	 <81c9245ec2dc3202ae7477aa1c04fb53@apache.org>
 <224f323405041405435c4546a4@mail.gmail.com> <425E66FE.8020900@apache.org>
 <425EB93D.70600@gmx.ch>
In-Reply-To: <425EB93D.70600@gmx.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jakob Braeuchi wrote:
> yes, the m_fields were introduced by me.
> the company i work for uses this standard and when i first saw it, i 
> found it totally useless. i'm an old smalltalker and was used to access 
> all instVars by getters and setters, so i didn't care about the name of 
> the instVar itself. in java code i found that most instVars were 
> accessed directly, and sometimes even temVars or parameters had the same 
> name as the instVars. so after all the m_ prefix looked quite useful, 
> because it let's me spot the access to instVars quickly.

You are right, I didn't think about the encapsulation issue.

However, I think it is more of a Java de-facto standard to name getters
and setters according to the members name. At least with IntelliJ IDEA
refactoring tools you can then rename getters/setters and all callers of
those automagically when you rename a memeber variable (which is not
possible for "protected String m_foo;" vs "public String getFoo();").

But I don't have a huge issue with "m_" prefixes for members and will
happily use whatever the majority decides on. :-)

Just as long as we decide which one to use in the naming standard.

Cheers,
  Martin

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org