+1 Accessor
That's the Java idiom. Not putting an accessor for an instance variable
means "Don't use this. It may be public, but it is a gross hack to make
something else work".
I assume this interface will be for Java programmers not C programmers?
My guess is that the performance difference optimizes to close to zero, and
you don't break a well known idiom without a good reason.
Oh, and hi everyone, been lurking for quite a while. :-)
-Brian
----- Original Message -----
From: "Alexander Mueller" <alex@littleblue.de>
To: <dev@subversion.tigris.org>
Sent: Friday, November 30, 2001 9:29 AM
Subject: PUBLIC POLL: final static
> Hi! It's poll time!
>
> There are some classes in the Java / Subversion binding that use public
variables.
> They are NOT variables with common read/write access. They are initialized
through
> the class constructor. After this they remain constant for the rest of the
instance lifetime.
> Example in class Entry:
> "public final Date text_time;"
>
> The reason for this kind of implementation is a performance improvement.
>
> The alternative would be to have accessor methods.
>
> Now its up to you.
>
> If you want it implemented as it is reply to this email and append
"VARIABLE" to the subject of the message.
> If you want to have it changed to accessor methods, reply to this email
and append "ACCESSOR" to the subject of the message.
>
> On next Thursday I will count the emails.
>
> Thanks for your participation...
> Have a nice weekend
>
> Alex
>
> P.S.: one vote per person, please... ;-)
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:50 2006