+1
This is absolutely essential in creating clean interfaces; if methods
and attributes are made unneccessarily public, it clutters the API
with misleading information.
Unfortunately, it's not possible for non-authors to make this call,
so the onus is on the class authors to comb through their code. An
outsider is going to have trouble knowing which methods are clearly
part of the _implementation_ of the class and which are parts of
the public or protected API.
our default javadocs should generate a list of public identifiers
only, and leave it as an exercise to the reader to generate private or
protected (ok, I'd allow public/protected as the default since a lot
of using Turbine is subclassing base objects).
--
Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications Inc
Business Innovations Through Open Source Systems: http://www.teledyn.com
"Computers are useless. They can only give you answers."(Pablo Picasso)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
