• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

documenting anonymous classes

 
Roman Rytov
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My GUI class uses a lot of anonymous internall classes. Is there any way to exclude them from being documented? It looks very ugly (I have about 10 such classes).
Any ideas to manage this situation?
 
Enrico Mannarino
Ranch Hand
Posts: 133
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've just one. Maybe I don't see the picture here, but why on earth do you ned 10 for?
About documentaion, I'll think public it's just enough.
I hope that my asnwer will help a bit?!
 
Thomas Smets
Ranch Hand
Posts: 111
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Y don't U simply make the protected / default & request the documentation to only publish the public ones ?

[ January 29, 2002: Message edited by: Thomas SMETS ]
 
Gennady Shapiro
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thomas is correct. You anonymous classes have default accessibility, the FBN spec requres documentation ONLY for public members. So no, you dont need to write docs on those.
And my advice -- don't over do it. It seems that you are being overly diligent. Extra effort does not earn extra points here.
 
Roman Rytov
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sorry gyus for confusion.
What I got in my docs is like this:
Inner classes inherited from class javax.swing.JFrame
it's not fully documented but just mentioned. Is it ok?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic