Re: Subprocedure invocation (was on RPG List) -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Subprocedure invocation (was on RPG List)
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Wed, 09 Jan 2008 12:47:55 -0600
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

Joe Pluta wrote:

Correct. setMyvar and getMyvar ("isMyvar" in the case of a Boolean) are
conventions. However, they're conventions that are followed by all IDEs and
indeed are required by certain J2EE functions. If you DON'T name your
getters and setters properly, you will probably cause yourself some extra
complexity down the road.

It's the basis of the whole Bean concept, isn't it?

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Subprocedure invocation (was on RPG List) , Joe Pluta

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.