Is it a bad programming practice to have "Public" members inside an "Internal" class?
Posted
by Amby
on Stack Overflow
See other posts from Stack Overflow
or by Amby
Published on 2010-06-09T14:49:11Z
Indexed on
2010/06/09
16:32 UTC
Read the original article
Hit count: 143
I mean, won;t it be more specific and appropriate if i "only" keep "protected","internal" and "private" members (field,method,property,event) in a class which is declared as "internal" ?
I have seen this practice ( having "public" members in an "internal" class) in various code so just wanted to know is it a bad practice or does it has some benefit or advantage.
[Only concerned about C#] Thanks for your interest.
© Stack Overflow or respective owner