Language Reference/Basic Concepts/Object System - Revision history

Thomas Linder Puls: review

2025-08-20T12:26:53Z

review

Thomas Linder Puls: subarticle

2013-02-12T09:35:02Z

subarticle

← Older revision		Revision as of 11:35, 12 February 2013
Line 72:		Line 72:
	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.

	<noinclude>{{LanguageReferenceSubarticle\|~~{{PAGENAME}}~~}}</noinclude>		<noinclude>{{LanguageReferenceSubarticle\|Basic Concepts/Object System}}</noinclude>

Thomas Linder Puls: subarticle

2013-02-12T09:29:42Z

subarticle

← Older revision		Revision as of 11:29, 12 February 2013
Line 72:		Line 72:
	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.

	<noinclude>{{LanguageReferenceSubarticle\|~~Basic Concepts/Object System~~}}</noinclude>		<noinclude>{{LanguageReferenceSubarticle\|{{PAGENAME}}}}</noinclude>

Thomas Linder Puls: subarticle

2013-02-12T09:17:17Z

subarticle

← Older revision		Revision as of 11:17, 12 February 2013
Line 71:		Line 71:

	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.
	<noinclude>~~[[Category:Language Reference Subarticle\|~~{{~~PAGENAME~~}}]]</noinclude>
			<noinclude>{{LanguageReferenceSubarticle\|Basic Concepts/Object System}}</noinclude>

Thomas Linder Puls: /* Code Inheritance */ sub

2012-10-25T15:41:16Z

Code Inheritance: sub

← Older revision		Revision as of 17:41, 25 October 2012
Line 71:		Line 71:

	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.
			<noinclude>[[Category:Language Reference Subarticle\|{{PAGENAME}}]]</noinclude>
	<noinclude>[[Category:Language Reference Subarticle]]</noinclude>

Thomas Linder Puls: symonym clarification

2009-05-05T11:18:25Z

symonym clarification

← Older revision		Revision as of 13:18, 5 May 2009
Line 70:		Line 70:
	===== Code Inheritance =====		===== Code Inheritance =====

	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child'' class ~~and~~ ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child''-class or ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.

	<noinclude>[[Category:Language Reference Subarticle]]</noinclude>		<noinclude>[[Category:Language Reference Subarticle]]</noinclude>

Thomas Linder Puls: Clarify class : interface name

2009-05-05T11:12:48Z

Clarify class : interface name

← Older revision		Revision as of 13:12, 5 May 2009
Line 42:		Line 42:
	We never have direct access to an object state, we always access an object state by means of a reference to the object and while an object is only identical to itself, we can have many references to the same object. Thus, the same object can be accessed through many different references.		We never have direct access to an object state, we always access an object state by means of a reference to the object and while an object is only identical to itself, we can have many references to the same object. Thus, the same object can be accessed through many different references.

	Classes and interfaces are also unique; they are identified by their names. Two interfaces or classes cannot have the same name in the same program (a class and an interface ~~also cannot~~ have the same name).		Classes and interfaces are also unique; they are identified by their names. Two interfaces or classes cannot have the same name in the same program. A class and an interface can only have the same name if the class constructs objects of that interface.

	The essence is that structural equality does '''not''' imply identity for objects, classes nor interfaces.		The essence is that structural equality does '''not''' imply identity for objects, classes nor interfaces.

Thomas Linder Puls: wikipedia link for semi-lattice

2009-05-05T11:10:15Z

wikipedia link for semi-lattice

← Older revision		Revision as of 13:10, 5 May 2009
Line 18:		Line 18:
	An ''interface'' is an object type. It has a name and defines a set of named object predicates.		An ''interface'' is an object type. It has a name and defines a set of named object predicates.

	Interfaces are structured in a ''supports'' hierarchy (the structure is a semi-lattice rooted in the interface object). If an object has a type denoted by an interface, then it also has the type of any supported interfaces. Therefore, the supports hierarchy is also a type hierarchy. An interface is a subtype of all its supported interfaces. We also say that the object ''supports'' the interface. If the interface is named ''X'', then we say that the object is an ''X'', or an ''X'' object.		Interfaces are structured in a ''supports'' hierarchy (the structure is a [[wikipedia:semilattice\|semi-lattice]] rooted in the interface <vp>object</vp>). If an object has a type denoted by an interface, then it also has the type of any supported interfaces. Therefore, the supports hierarchy is also a type hierarchy. An interface is a subtype of all its supported interfaces. We also say that the object ''supports'' the interface. If the interface is named ''X'', then we say that the object is an ''X'', or an ''X'' object.

	===== Class =====		===== Class =====

Thomas Linder Puls: Categorized

2008-10-29T19:52:09Z

Categorized

← Older revision		Revision as of 21:52, 29 October 2008
Line 72:		Line 72:
	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child'' class and ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child'' class and ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.

	<noinclude>[[Category:Language Reference ~~Article~~]]</noinclude>		<noinclude>[[Category:Language Reference Subarticle]]</noinclude>

Thomas Linder Puls: Categorized

2008-10-29T19:51:27Z

Categorized

← Older revision		Revision as of 21:51, 29 October 2008
Line 72:		Line 72:
	In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child'' class and ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.		In Visual Prolog code inheritance only takes place in the implementation of a class. Visual Prolog has multiple inheritance. You inherit from a class by mentioning the class in a special ''inherits'' section of the implementation. The classes you inherit from are called ''parent'' classes or ''super''-classes. ''Child'' class and ''sub''-class is the dual to parent class, we also say that the child classes ''inherit'' from the parent classes. A child class can only access its parent classes through its public interface, i.e. it does not receive any extra privileges than anybody else that use the parent class.

	<noinclude>[[Category:Language Reference ~~Subpage~~]]</noinclude>		<noinclude>[[Category:Language Reference Article]]</noinclude>