omit the pirvate/public etc

[Wilfried Mestdagh]

Hi,

If you omit private / public / protected etc in a declaration then What is
it ? pirvate, protected ?

eg:
bool test;
bool check
{
return (something == false);
}

--
rgds, Wilfried
http://www.mestdagh.biz

[Jay]

Default is always private.

- Jay

"Wilfried Mestdagh" <Wi**************@discussions.microsoft.com> escreveu na
mensagem news:B4**********************************@microsof t.com...

Hi,

If you omit private / public / protected etc in a declaration then What
is
it ? pirvate, protected ?

eg:
bool test;
bool check
{
return (something == false);
}

--
rgds, Wilfried
http://www.mestdagh.biz

[Uchiha Jax]

private
"Wilfried Mestdagh" <Wi**************@discussions.microsoft.com> wrote in
message news:B4**********************************@microsof t.com...

Hi,

If you omit private / public / protected etc in a declaration then What is it ? pirvate, protected ?

eg:
bool test;
bool check
{
return (something == false);
}

--
rgds, Wilfried
http://www.mestdagh.biz

[Bruce Wood]

The default depends upon what you are declaring:

http://msdn.microsoft.com/library/de...spec_3_5_1.asp

"...when a member declaration does not include any access modifiers,
the context in which the declaration takes place determines the default
declared accessibility.

"Namespaces implicitly have public declared accessibility. No access
modifiers are allowed on namespace declarations.
"Types declared in compilation units or namespaces... default to
internal declared accessibility.
"Class members... default to private declared accessibility.
"Struct members... default to private declared accessibility because
structs are implicitly sealed.
"Interface members implicitly have public declared accessibility. No
access modifiers are allowed on interface member declarations.
"Enumeration members implicitly have public declared accessibility. No
access modifiers are allowed on enumeration member declarations.

[Jay]

You're right. I just considered the defaults for variables.

-Jay

"Bruce Wood" <br*******@canada.com> escreveu na mensagem
news:11********************@o13g2000cwo.googlegrou ps.com...

The default depends upon what you are declaring:

http://msdn.microsoft.com/library/de...spec_3_5_1.asp

"...when a member declaration does not include any access modifiers,
the context in which the declaration takes place determines the default
declared accessibility.

"Namespaces implicitly have public declared accessibility. No access
modifiers are allowed on namespace declarations.
"Types declared in compilation units or namespaces... default to
internal declared accessibility.
"Class members... default to private declared accessibility.
"Struct members... default to private declared accessibility because
structs are implicitly sealed.
"Interface members implicitly have public declared accessibility. No
access modifiers are allowed on interface member declarations.
"Enumeration members implicitly have public declared accessibility. No
access modifiers are allowed on enumeration member declarations.

[Jon Skeet [C# MVP]]

Wilfried Mestdagh <Wi**************@discussions.microsoft.com> wrote:

If you omit private / public / protected etc in a declaration then What is
it ? pirvate, protected ?

It's always the most private it can be - so for top-level types it's
internal, for member variables it's private, etc.

This is a really good default setting, as it means you can omit the
access modifier and be on the safe side - any access modifier means
that you're deliberately making it more public.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too