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

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

Cross Ref Guide

JAVALANGUAGE

Java

JAVAANDDELPHITOC

Overview

+Tool Basics

Report Tools Overview

+Language Basics

+Language Details

+Data Structures

Array

+Statements

+Operators

+OOP Basics

Member Visibility◄╣

+OOP Details

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

► KB ► To/From Guides ► Java

Print This

Member Visibility (Java and Delphi Cross Reference Guide)

By Mike Prestwood

Java versus Delphi: A side by side comparison between Java and Delphi.

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:

In Delphi, you group member declarations as part of defining the interface for a class in the Interface section of a unit.

Up until D2005, private and protected were not implemented strictly. Starting with D2005, a traditional strict versions of OOP are supported using the strict keyword. OO purist will want you to use strict private over private and strict protected over protected. I suggest you follow that advice until you both fully understand the differences and have a specific need.

Delphi offers a special published specifier which is the same as public members but runtime type information (RTTI) is generated.

Syntax Example:

TCyborg = class(System.Object)
private
  //Don't use accept when you really want private friendly members.
strict private
  //Use as your default private members.

  FName: String;
protected
  //Don't use accept when you really want protected friendly members.

strict protected
  //Use as your default protected members.

public

  

published

  //RTTI Info

end;

Delphi Member Visibility 1 certification question.

Ref: /ASPSuite/KB/Document_View.asp?QID=100889