When defining a class as internal, do you define what would usually be public fields as internal?

Posted by devoured elysium on Stack Overflow See other posts from Stack Overflow or by devoured elysium
Published on 2010-05-03T10:13:30Z Indexed on 2010/05/03 10:18 UTC
Read the original article Hit count: 276

Filed under:
|
|
|

When defining a class as internal, do you define what would usually be public fields as internal? Or do you leave them as public? I have a set of classes with public/private methods that I have decided to set as internal. Now, should I change the class' modifier to internal and let the rest of the methods/properties as they are (public/private) or switch them to (internal/private)?

I don't see a big point in changing it to internal, and if by some reason later I want to set them back to public it's going to give a lot of work to have to put them back to public again.

Any other thoughts on this?

© Stack Overflow or respective owner

Related posts about subjective

Related posts about namespaces