View Single Post
  #1 (permalink)  
Old July 12th, 2015, 01:38 AM
lmstearn lmstearn is offline
Registered User
Points: 5, Level: 1
Points: 5, Level: 1 Points: 5, Level: 1 Points: 5, Level: 1
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Jul 2015
Location: Australia
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Smile Protected Internal Members

Hi there,
This is my first post here, so please be kind
Have gone through the early chapters of this excellent book to great benefit.
A little question regarding the definition of 'protected internal' in page 242.

The last two of these can be combined, so protected internal members are also possible. These are
only accessible from code-derived classes within the project (more accurately, the assembly).
Other definitions follow along the lines of
'protected internal' allows the member to be available anywhere in the assembly in addition to any classes inheriting the class (in the assembly or not).
Do they mean the same thing?
Thanks in advance.

Well, while we're here, on page 257 it states:
Interface members can’t be defined using the keywords static , virtual , abstract , or
yet on page 259
It is possible to implement interface members using the keyword virtual or abstract , but not static
or const .
This is slightly confusing. Anyone able to clear the fog?

Last edited by lmstearn; July 12th, 2015 at 08:32 AM.. Reason: Minor edit