Comments on: variables – public/protected/private/internal/static

By: pookka

pookka — Mon, 15 Feb 2010 09:47:28 +0000

All types and type members have an accessibility level, which controls whether they can be used from other code in your assembly or other assemblies. You specify the accessibility of a type or member when you declare it by using one of these access modifiers:

public

The type or member can be accessed by any other code in the same assembly or another assembly that references it.

private

The type or member can only be accessed by code in the same class or struct.

protected

The type or member can only be accessed by code in the same class or struct, or in a derived class.

internal

The type or member can be accessed by any code in the same assembly, but not from another assembly.

protected internal

The type or member can be accessed by any code in the same assembly, or by any derived class in another assembly.

By: smedini

smedini — Wed, 06 May 2009 08:10:54 +0000

The column internal is wrong.
The descendant of Class should be Deny.

You can say it’s package internal and hierarchy protected.

By: Mario Ruggier

Mario Ruggier — Mon, 04 May 2009 09:55:40 +0000

Thanks, useful little summary table (helps to remember the frequently badly explained difference between internal and protected).

But, would it not be more logical to switch the Internal and Protected columns? Like that the natural restriction-level progression is more evident… i.e. the table becomes:

Code placement			Private		Protected 	Internal	Public

Same class				Allow		Allow		Allow		Allow
Descendants of class	Deny		Allow		Allow		Allow
Classes in same package	Deny		Deny		Allow		Allow
Other package			Deny 		Deny 		Deny		Allow

By: Virgil Cristea

Virgil Cristea — Mon, 16 Feb 2009 09:45:11 +0000

You are right. I will modify it.

By: Daniel Rijkhof

Daniel Rijkhof — Sun, 15 Feb 2009 11:10:00 +0000

Let me add… that comment was about flex (as) 3

By: Daniel Rijkhof

Daniel Rijkhof — Sun, 15 Feb 2009 11:08:32 +0000

Data is not correct :/

Code placement Private Internal Protected Public
Classes in same package Deny _Allow_ _Deny_ Allow

By: Erno

Erno — Thu, 13 Nov 2008 22:36:49 +0000

Hi! This was good and simple. But what is static ? You didn’t tell that. Well this is old post and I google it right away, but maybe next one need to know that.

Thanks!

By: Links for the Weekend, 4-19-2008

Links for the Weekend, 4-19-2008 — Sat, 19 Apr 2008 13:42:22 +0000

[...] Variables – Public/Protected/Private/Internal/Static – ActionScript, Flex resources… [...]

By: House of Code

House of Code — Fri, 21 Mar 2008 20:25:41 +0000

The Science of Packages

Everyone knows about packages, but do you know of the science of packages? There are quite a few principles that deal with maintainability and reusability. Read on to learn about them, as explained by Robert C. Martin.
…

By: Significance of package names - Ultrashock Forums

Significance of package names - Ultrashock Forums — Fri, 21 Mar 2008 15:07:59 +0000

[...] in regards to exposing classes and interfaces to the public. For example, you can make classes package protected so that users outside that package cannot use that class. An example is that you do have a public [...]