access-modifiers

This question already has an answer here: Why and how does C# allow accessing private variables outside the class itself when it's within the same containing class? 3 answers If I have ObjectA, and it has a private method GetPrice() and also has a "parent" field of the same type, why am I able to call GetPrice() on the parent instance from within the child instance? Example: private decimal GetPrice() { ObjectA parent = Parent; if(parent != null) { return parent.GetPrice(); // Why is this OK? } return 0; } Because private means "not accessible to other types ", not "not accessible to other

I understand that the rule of thumb in OOD is to minimize access to all members of a given object as best as can be reasonably accomplished. C# and Java both seem to implement the same set of access modifiers; however, something which has bewildered me for some time now is why Java classes seem to be mostly declared as public while C# classes seem mostly to be declared as default. Is there some subtlety to these languages which imposes these differences, or is it simply a matter of convention or what? I find myself frequently going through my C# code (I habitually make most classes public,

When I right click on a class (that is part of an third party assembly - not code I have written) in Visual Studio and select "Go to Definition", I can see all the methods, properties etc of the class. I notice all these are all public and no private (or any other level of access) members are shown. Does this feature only show public members of the class? You can find the answer on the doc page : When you try to run the Go To Definition or Peek Definition command for types or members that are marked as internal, Visual Studio does not display their metadata as source code, regardless of

I've been working with the prototype library for some time now and occasionally find myself wishing I had multiple access levels (public, private, and protected). The closest I've come so far is the following: SampleBase = Class.create({ /* virtual public constructor */ initialize: function(arg1, arg2) { // private variables var privateVar1, privateVar2; // private methods var privateMethod1 = function() { } function privateMethod2() { } // public (non virtual) methods this.publicNonVirtual1 = function() { return privateVar1; } this.publicNonVirtual2 = function() { return privateVar2; } }, //

I have alluded to this issue in my other question , but i think it's worthwhile breaking it out into its own question, as it's not really dependant on the other scenarios i mentioned. Anyways - onto the Q, don't know if this is possible. Looking for a solution/workaround. I have a Class Library, with nothing but POCO's: MyCompany.MyProject.Domain.POCO This assembly has a POCO like this: public class Post { public int PostId { get; set; } public int Name { get; set; } ... } Now, i have another Class Library, which is my DAL/Repository, and uses Entity Framework 4.0 for the persistence:

Java specification allows a class with default access to have its constructor public access, what is the purpose of it, since it cannot be referenced outside its package? I wanted to make this a comment, but since no code tags are allowed in comments.... In regards to your comment on CristopheDs answer: package bob; class MySuperHiddenClass { public MySuperHiddenClass() { System.out.println("bob"); } } And package bob; public class MyPublicClass extends MySuperHiddenClass { } No constructor was declared in MyPublicClass, but you can still call new MyPublicClass from any package. If you are