Require Comments based on visibility per Member

Topics: User Forum
Jan 22, 2007 at 8:33 PM
Currently it's only possible to say :

Public Properties, public Classes and so on...
Private Properties, private Classes and so on...

It isn't possible to say:

Protected properties, public classes and no protected classes...

May it would be better to let the user choose "properties" and add "protected"... choose "classes" and add "public".

Currently we dont have such a requirement but who knows what future will require ;)
So if it isn't that much work to implement I would suggest adding this feature.

Jan 22, 2007 at 8:49 PM
I intentionally didn't implement the all-out matrix of possible combinations of elements and visibility. Aside from the fact that it would have complicated things code-wise, the main reasoning was "Which elements will need code comments when we talk about reuseable libraries? Public elements." - thus reducing the problem space by one dimension.

Currently, no plans to change that.