Comments on: Internal And Protected http://agsmith.wordpress.com/2007/12/15/internal-and-protected/ Random Thoughts about C#, VS, WinForms, WPF and .NET in General Tue, 22 Dec 2009 20:10:23 +0000 http://wordpress.com/ hourly 1 By: Alex Sarafian http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-21 Alex Sarafian Mon, 17 Dec 2007 21:43:05 +0000 http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-21 I fully understood what you explained. I just thought from my expierence that two keywords interact with the AND logic, but from what you explained I was mistaken. Anyway thanks again for your answer. Nice solution though. I fully understood what you explained. I just thought from my expierence that two keywords interact with the AND logic, but from what you explained I was mistaken.

Anyway thanks again for your answer.
Nice solution though.

]]> By: agsmith http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-20 agsmith Mon, 17 Dec 2007 15:09:39 +0000 http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-20 Hi Alex. Actually what you are describing - internal protected - is what the clr refers to as AssemblyOrFamily (or you might think of it as InternalOrProtected). This means that the member may be accessed by someone internally in the assembly OR by any derived class even one that is in another assembly. I described this in the blurb on scopes. The scope that is not supported currently is InternalAndProtected meaning that only members that are within that assembly AND derived from the class may access the member. I agree that we should not need to use reflection to do what the compiler should be handling for us. I merely offered the reflection approach as a way to try and enforce what is not currently supported. Hi Alex. Actually what you are describing – internal protected – is what the clr refers to as AssemblyOrFamily (or you might think of it as InternalOrProtected). This means that the member may be accessed by someone internally in the assembly OR by any derived class even one that is in another assembly. I described this in the blurb on scopes. The scope that is not supported currently is InternalAndProtected meaning that only members that are within that assembly AND derived from the class may access the member. I agree that we should not need to use reflection to do what the compiler should be handling for us. I merely offered the reflection approach as a way to try and enforce what is not currently supported.

]]> By: Alex Sarafian http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-19 Alex Sarafian Mon, 17 Dec 2007 09:45:34 +0000 http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-19 Mr Smith recently I had the same problem. What I hadn't realized was that intentionally protected internal scope allows class that inherit my class to use the protected internal member. I thought it was a bug. Now I realize that it is a not so good implementation in Object oriented approach. As i understand it a logic & applies to scopes. protected allows children class to access protected members of the father internal allows only class from the specific assebly to access specified members. So if you apply the & bitwise logic to protectd & internal, the natural conclution is what we both expected. That's why i first thought of it as a bug. Personaly I believe that it is a huge problem, and being forced to used a solution like yours is not very appealing thought usefull if it comes to that. I should not be forced to use reflection nor by any means allow the consumer of my control understand that there are members that i have made tricks to protect from accessing. Thank you. Mr Smith recently I had the same problem. What I hadn’t realized was that intentionally protected internal scope allows class that inherit my class to use the protected internal member.

I thought it was a bug. Now I realize that it is a not so good implementation in Object oriented approach. As i understand it a logic & applies to scopes.
protected allows children class to access protected members of the father
internal allows only class from the specific assebly to access specified members.

So if you apply the & bitwise logic to protectd & internal, the natural conclution is what we both expected. That’s why i first thought of it as a bug.

Personaly I believe that it is a huge problem, and being forced to used a solution like yours is not very appealing thought usefull if it comes to that.

I should not be forced to use reflection nor by any means allow the consumer of my control understand that there are members that i have made tricks to protect from accessing.

Thank you.

]]> By: Josh Smith http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-11 Josh Smith Sat, 15 Dec 2007 22:49:16 +0000 http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-11 Holy smokes!! This is really amazing stuff. I agree with Karl, your blog is going to develop a cult-like following if you keep this up! :) Josh Holy smokes!! This is really amazing stuff. I agree with Karl, your blog is going to develop a cult-like following if you keep this up! :)

Josh

]]> By: Internal And Protected Virtual « Andrew Smith http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-10 Internal And Protected Virtual « Andrew Smith Sat, 15 Dec 2007 21:26:15 +0000 http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-10 [...] Andrew Smith Random Thoughts about C#, VS, WinForms, WPF and .NET in General « Internal And Protected [...] [...] Andrew Smith Random Thoughts about C#, VS, WinForms, WPF and .NET in General « Internal And Protected [...]

]]> By: Karl Shifflett http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-8 Karl Shifflett Sat, 15 Dec 2007 10:14:55 +0000 http://agsmith.wordpress.com/2007/12/15/internal-and-protected/#comment-8 Andrew, Deep, brother Deep! Your blog will quickly get a huge following. One problem. Mole forget to read your work and by-passes the scope attributes to display "hidden data". :-) Best to you, Karl Andrew,

Deep, brother Deep!

Your blog will quickly get a huge following.

One problem. Mole forget to read your work and by-passes the scope attributes to display “hidden data”. :-)

Best to you,

Karl

]]>