To/From Code

	Languages
BROWSEBYLANGUAGE Access VBA ASP Classic C# C++ C++/CLI Corel Paradox Delphi Delphi Prism Java JavaScript Perl PHP VB Classic VB.Net

	Categories
BROWSEBYCATEGORY +Tool Basics +Language Basics +Language Details +Data Structures +Statements +Operators +Commands +Database +OOP Basics +OOP Details

	C++/CLI Guides
C++/CLI To/From Conversion Guides C++/CLI and Access VBA C++/CLI and ASP Classic C++/CLI and C# C++/CLI and C++ C++/CLI and Corel Paradox C++/CLI and Delphi C++/CLI and Java C++/CLI and JavaScript C++/CLI and Perl C++/CLI and PHP C++/CLI and VB Classic C++/CLI and VB.Net

Cross Ref Guide

C++/CLILANGUAGE

C++/CLI

C++/CLIANDDELPHI PRISMTOC

Overview

+Tool Basics

Report Tools Overview

+Language Basics

+Language Details

+Statements

+Operators

+OOP Basics

Member Visibility◄╣

+OOP Details

	Members-Only
Sign in to see member-only pages.

► KB ► To/From Guides ► C++/CLI

Print This

Member Visibility (C++/CLI and Delphi Prism Cross Reference Guide)

By Mike Prestwood

C++/CLI versus Delphi Prism: A side by side comparison between C++/CLI and Delphi Prism.

OOP Basics

Some languages support object-based concepts such as Paradox, Access, and VB Classic. Other languages have OO extensions and fully support object orientation in a hybrid fashion (such as C++ and Dephi for Win32). Finally, some lanages such as C#, VB.Net, Prism, and Java are entirely written in OO. Meaning, every line of code written must occur within a class).

Member Visibility

[Other Languages]

General Info: Class Visibility Specifiers

In OOP languages, members of a class have a specific scope that indicates visibility. Standard visibility includes private, protected, and public. Private members are usable by the defining class only (fully encapsulated). They are invisible outside of the class except by friendly classes. Protected members are usable by the defining class and descendant classes only (plus friendly classes). Public members are usable wherever its class can be referenced.

Languages Focus

Traditional member visibility specifiers for fully OOP languages are private, protected, and public. Many modern OOP languages implement additional member visibilities.

Additional member modifiers are documented under the Member Modifiers topic.

[Not specified yet. Coming...]

Delphi Prism: "Class Member Visibility Levels"

In Prism, you specify each class and each class member's visibility with a Class Member Visibility Level preceding the return type. Like Delphi, you group member declarations as part of defining the interface for a class in the Interface section of a unit.

Unlike Delphi, Prism supports a traditional OO approach to member visibility with additional .Net type assembly visibility. For example, private members are truly private to the class they are declared in. In Delphi for Win32, you use strict private for true traditional private visibility.

Prism also supports assembly and protected and assembly or protected which modify the visibility of protected members to include only descendants in the same assembly (and) or publicly accessible from assembly and descendant only outside (or). OO purist might object to assembly and protected and assembly or protected and I suggest you choose the traditional private, protected, and public as your first chose at least until you both fully understand them and have a specific need for them.

Syntax Example:

Cyborg = public class(System.Object)
private

  //private properties, methods, etc. here.

  FName: String;

protected

  //protected properties, methods, etc. here.

assembly and protected

  //properties, methods, etc. here.

assembly or protected

  //properties, methods, etc. here.

public

  //properties, methods, etc. here.

end;

Delphi Prism Class Member Visibility Levels 1 certification question.