The short of it is you can get around public, private etc with
reflection anyway, so why slow down the entire system just because
you're under the incorrect assumption you can "force" api consumers to
do anything?
If it's that flaming important, sick the lawyers on 'em. That's what
they're for.
-Josh
--
"His comrades fought beside him, Van Owen and the rest...
But of all the thompson gunners- Roland was the best."
Josh McDonald
Analyst Programmer
Information Technology
Ph: 61 7 3006 6460
Email: [EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 17/02/2006 9:53:25 am >>>
Wow.
Why not
method(args, this);
so you know the calling object.
or better version.
register(this);
method(arg);
Plenty of OO designs.
Or just don't make it public, there are 3 "modifier" choices left other
then public, including package/friend.
I would just expose an API interface and have comments "for internal
use" for implementation, which I would then not JavaDoc! Just JavaDoc
the API interface.
.V
Frank W. Zammetti wrote:
> I saw a very similar question asked a few months back in a general
Java
> forum, and I suggested an answer that I've never had the chance to
> actually try out... the theory is interesting though...
>
> In the method you want to "protect", immediately throw an exception
and
> catch it. Then, parse the stack trace and see who the caller was.
If
> it's not a class you want to have access to the method, throw an
> IllegalAccessException.
>
> Again, it's one of those things that sounds good in your head, I have
no
> idea if it translates to anything workable :)
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
***************************************************************************
Messages included in this e-mail and any of its attachments are those
of the author unless specifically stated to represent WorkCover Queensland. The
contents of this message are to be used for the intended purpose only and are
to be kept confidential at all times.
This message may contain privileged information directed only to the intended
addressee/s. Accidental receipt of this information should be deleted promptly
and the sender notified.
This e-mail has been scanned by Sophos for known viruses.
However, no warranty nor liability is implied in this respect.
****************************************************************************
