Object oriented programming in SOUL - Revision history

JDamon: User Language is non-procedural

2021-12-13T20:09:44Z

User Language is non-procedural

← Older revision		Revision as of 20:09, 13 December 2021
Line 9:		Line 9:
	Overloading is also not supported, but [[Methods#Optional and default parameters\|optional parameters]] provide much more easily most of what overloading is used for, and [[Methods#Named parameters\|named parameters]] enhance this capability.		Overloading is also not supported, but [[Methods#Optional and default parameters\|optional parameters]] provide much more easily most of what overloading is used for, and [[Methods#Named parameters\|named parameters]] enhance this capability.

	<var class="product">SOUL</var> without OOP generally corresponds to a [~~http~~://en.~~wikipedia~~.~~org~~/~~wiki~~/~~Procedural_programming~~ procedural programming language].		<var class="product">SOUL</var> without OOP generally corresponds to a [https://www.pcmag.com/encyclopedia/term/non-procedural-language non-procedural programming language].

	If you are an experienced <var class="product">User Language</var> programmer, you are likely to benefit from [[Getting started with OOP for User Language programmers]].		If you are an experienced <var class="product">User Language</var> programmer, you are likely to benefit from [[Getting started with OOP for User Language programmers]].

Goff: Fix URL for interfaces

2016-10-17T22:16:55Z

Fix URL for interfaces

← Older revision		Revision as of 22:16, 17 October 2016
Line 6:		Line 6:
	<var class="product">SOUL</var> OOP supports many but not all the concepts		<var class="product">SOUL</var> OOP supports many but not all the concepts
	discussed in books about object-oriented programming.		discussed in books about object-oriented programming.
	Specifically there is no explicit support for [http://en.wikipedia.org/wiki/Interface_(~~8object~~-oriented_programming) interfaces], though [[Inheritance and polymorphism#Multiple inheritance\|multiple inheritance]] provides all the functionality provided by interfaces with more flexibility.		Specifically there is no explicit support for [http://en.wikipedia.org/wiki/Interface_(object-oriented_programming) interfaces], though [[Inheritance and polymorphism#Multiple inheritance\|multiple inheritance]] provides all the functionality provided by interfaces with more flexibility.
	Overloading is also not supported, but [[Methods#Optional and default parameters\|optional parameters]] provide much more easily most of what overloading is used for, and [[Methods#Named parameters\|named parameters]] enhance this capability.		Overloading is also not supported, but [[Methods#Optional and default parameters\|optional parameters]] provide much more easily most of what overloading is used for, and [[Methods#Named parameters\|named parameters]] enhance this capability.

JAL: add link

2015-07-23T21:19:53Z

add link

← Older revision		Revision as of 21:19, 23 July 2015
Line 73:		Line 73:
	<dd>A standard layout of variables. A structure is similar to an image, except a structure can have many instances while an image can only have one. Structure variables have the layout indicated by the structure definition, and they can be assigned to each other. Structures are different from objects in that structures are passed by value rather than by reference. Structures can be thought of as composite datatypes.		<dd>A standard layout of variables. A structure is similar to an image, except a structure can have many instances while an image can only have one. Structure variables have the layout indicated by the structure definition, and they can be assigned to each other. Structures are different from objects in that structures are passed by value rather than by reference. Structures can be thought of as composite datatypes.

	<dt>[[~~Methods~~\|Subroutine]]		<dt>[[Classes and Objects#Method declarations and method types\|Subroutine]]
	<dd>A method that does not return a value and cannot be set, that is, appear on the left side of an assignment. The term <strong>subroutine</strong> is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way, though in VB subroutines are denoted by the word Sub.		<dd>A method that does not return a value and cannot be set, that is, appear on the left side of an assignment. The term <strong>subroutine</strong> is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way, though in VB subroutines are denoted by the word Sub.

ELowell at 20:02, 11 November 2014

2014-11-11T20:02:38Z

← Older revision		Revision as of 20:02, 11 November 2014
Line 29:		Line 29:

	<dt>[[Collections\|Collection]]		<dt>[[Collections\|Collection]]
	<dd>A special class that, as the name suggests, is used to manage collections or groups of variables. A collection provides the same functionality as an array, though with much more flexibility. The term ~~'''~~collection~~'''~~ is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way, and it is a concept present in most object-oriented programming languages.		<dd>A special class that, as the name suggests, is used to manage collections or groups of variables. A collection provides the same functionality as an array, though with much more flexibility. The term <strong>collection</strong> is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way, and it is a concept present in most object-oriented programming languages.

	<div id="constructor"></div>		<div id="constructor"></div>
	<dt>[[Classes and Objects#Method declarations and method types\|Constructor]]		<dt>[[Classes and Objects#Method declarations and method types\|Constructor]]
	<dd>A method that processes an object immediately after the object is instantiated (created). The term ~~'''~~constructor~~'''~~ is standard object-oriented programming terminology, but although it does in <var class="product">SOUL</var>, it does not appear as an actual keyword in most object-oriented programming languages.		<dd>A method that processes an object immediately after the object is instantiated (created). The term <strong>constructor</strong> is standard object-oriented programming terminology, but although it does in <var class="product">SOUL</var>, it does not appear as an actual keyword in most object-oriented programming languages.

	<dt>[[Object variables#Discarding objects\|Discard]]		<dt>[[Object variables#Discarding objects\|Discard]]
Line 46:		Line 46:

	<dt>[[Methods\|Function]]		<dt>[[Methods\|Function]]
	<dd>A method that returns a value and cannot be set, that is, appear on the left side of an assignment. The term ''function'' is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way.		<dd>A method that returns a value and cannot be set, that is, appear on the left side of an assignment. The term <strong>function</strong> is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way.

	<dt>[[Intrinsic classes\|Intrinsic]] method		<dt>[[Intrinsic classes\|Intrinsic]] method
Line 58:		Line 58:

	<dt>[[Methods\|Method]]		<dt>[[Methods\|Method]]
	<dd>A block of code that performs a particular operation in a particular class. In <var class="product">SOUL</var> OOP, there are four kinds of methods: subroutines, functions, properties, and constructors. Methods can be ''shared'' that is, perform work independent of any instance of a class; or they can be ''non-shared'', that is, perform work on an object, a specific instance of a class.		<dd>A block of code that performs a particular operation in a particular class. In <var class="product">SOUL</var> OOP, there are four kinds of methods: subroutines, functions, properties, and constructors. Methods can be <strong>shared</strong> that is, perform work independent of any instance of a class; or they can be <strong>non-shared</strong>, that is, perform work on an object, a specific instance of a class.

	<dt>[[Classes and Objects\|Object]]		<dt>[[Classes and Objects\|Object]]
	<dd>A collection of information that describes some entity, often some "real world" entity such as a customer or an order or a part. Objects have state, that is, information contained in the object can change over time, usually as a result of methods (actions) performed against the object. Objects are never accessed directly but are accessed via ''references''. Most important among these references are [[Object variables\|object variables]] that, in <var class="product">SOUL</var>, look very much like regular %variables. The specific information held in an object and the methods (actions) available on an object are described by the object's class.		<dd>A collection of information that describes some entity, often some "real world" entity such as a customer or an order or a part. Objects have state, that is, information contained in the object can change over time, usually as a result of methods (actions) performed against the object. Objects are never accessed directly but are accessed via <strong>references</strong>. Most important among these references are [[Object variables\|object variables]] that, in <var class="product">SOUL</var>, look very much like regular %variables. The specific information held in an object and the methods (actions) available on an object are described by the object's class.

	<div id="methobj"></div>		<div id="methobj"></div>
Line 68:		Line 68:

	<dt>[[Methods#props\|Property]]		<dt>[[Methods#props\|Property]]
	<dd>A method that reflects the state of an object (class instance) or, in the case of a shared property, the state of the class as a whole. Properties can be ~~'''~~read-only~~'''~~ or ~~'''~~settable~~'''~~, that is, valid on the left side of an assignment statement. Properties appear to users of a class to be almost identical to class variables, but they actually have code behind them that is run when the property value is set or retrieved. The term ~~'''~~property~~'''~~ is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way.		<dd>A method that reflects the state of an object (class instance) or, in the case of a shared property, the state of the class as a whole. Properties can be <strong>read-only</strong> or <strong>settable</strong>, that is, valid on the left side of an assignment statement. Properties appear to users of a class to be almost identical to class variables, but they actually have code behind them that is run when the property value is set or retrieved. The term <strong>property</strong> is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way.

	<dt>[[Structures\|Structure]]		<dt>[[Structures\|Structure]]
Line 74:		Line 74:

	<dt>[[Methods\|Subroutine]]		<dt>[[Methods\|Subroutine]]
	<dd>A method that does not return a value and cannot be set, that is, appear on the left side of an assignment. The term ~~'''~~subroutine~~'''~~ is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way, though in VB subroutines are denoted by the word Sub.		<dd>A method that does not return a value and cannot be set, that is, appear on the left side of an assignment. The term <strong>subroutine</strong> is not standard object-oriented programming terminology, but it is used in Visual Basic in almost exactly the same way, though in VB subroutines are denoted by the word Sub.

	<dt>Variable		<dt>Variable

JAL: /* Object-oriented terminology */

2014-02-28T23:19:49Z

Object-oriented terminology

← Older revision		Revision as of 23:19, 28 February 2014
Line 22:		Line 22:

	To facilitate the initial learning process and to provide a quick reference for when the		To facilitate the initial learning process and to provide a quick reference for when the
	concepts become clearer, brief definitions of key object-oriented terms are described here:		concepts become clearer, brief definitions of key object-oriented terms are described here, and most of the terms are links to more detailed descriptions:

	<dl>		<dl>

JAL: /* Object-oriented terminology */

2014-02-28T23:12:29Z

Object-oriented terminology

← Older revision		Revision as of 23:12, 28 February 2014
Line 41:		Line 41:
	<dd>A special class that is used to denote a group of names with a limited set of values like, for example, "True" and "False". The term "enumeration" is not standard object-oriented programming terminology and, in fact, appears in many object-oriented languages as a procedural-language leftover often called "Enum".		<dd>A special class that is used to denote a group of names with a limited set of values like, for example, "True" and "False". The term "enumeration" is not standard object-oriented programming terminology and, in fact, appears in many object-oriented languages as a procedural-language leftover often called "Enum".

			<div id="exception"></div>
	<dt>[[Exceptions\|Exception]]		<dt>[[Exceptions\|Exception]]
	<dd>A class used to describe an error situation that is detected during the execution of a method. The method's code uses a <var>[[Throw statement\|Throw]]</var> statement to output an exception object (which must be specified in the method declaration). If the <i>code that invokes the method</i> is within a <var>[[Try block\|Try]]</var> block, it can use a <var>Catch</var> block, following the invocation and within the <var>Try</var> block, to respond to an exception and thereby to prevent request cancellation.		<dd>A class used to describe an error situation that is detected during the execution of a method. The method's code uses a <var>[[Throw statement\|Throw]]</var> statement to output an exception object (which must be specified in the method declaration). If the <i>code that invokes the method</i> is within a <var>[[Try block\|Try]]</var> block, it can use a <var>Catch</var> block, following the invocation and within the <var>Try</var> block, to respond to an exception and thereby to prevent request cancellation.

JAL at 17:15, 2 January 2014

2014-01-02T17:15:57Z

← Older revision		Revision as of 17:15, 2 January 2014
Line 11:		Line 11:
	<var class="product">SOUL</var> without OOP generally corresponds to a [http://en.wikipedia.org/wiki/Procedural_programming procedural programming language].		<var class="product">SOUL</var> without OOP generally corresponds to a [http://en.wikipedia.org/wiki/Procedural_programming procedural programming language].

	If you are an experienced <var class="product">User Language</var> programmer, you are likely to benefit from [[Getting started with ~~object-oriented programming~~ for User Language programmers]].		If you are an experienced <var class="product">User Language</var> programmer, you are likely to benefit from [[Getting started with OOP for User Language programmers]].

	==Object-oriented terminology==		==Object-oriented terminology==
Line 84:		Line 84:
	<li>[[Lists of classes and methods]]		<li>[[Lists of classes and methods]]
	<li>[[:Category:SOUL object-oriented programming topics\|SOUL object-oriented programming: collected topics]]		<li>[[:Category:SOUL object-oriented programming topics\|SOUL object-oriented programming: collected topics]]
	<li>[[Getting started with ~~object-oriented programming~~ for User Language programmers]]		<li>[[Getting started with OOP for User Language programmers]]
	</ul>		</ul>

	[[Category:SOUL]]		[[Category:SOUL]]
	[[Category:SOUL object-oriented programming topics]]		[[Category:SOUL object-oriented programming topics]]

JAL: /* Object-oriented terminology */

2013-10-23T18:35:10Z

Object-oriented terminology

← Older revision		Revision as of 18:35, 23 October 2013
Line 33:		Line 33:
	<div id="constructor"></div>		<div id="constructor"></div>
	<dt>[[Classes and Objects#Method declarations and method types\|Constructor]]		<dt>[[Classes and Objects#Method declarations and method types\|Constructor]]
	<dd>A method that processes an object immediately after the object is instantiated (created). The term '''constructor''' is standard object-oriented programming terminology, but it does not appear as an actual keyword in most object-oriented programming languages.		<dd>A method that processes an object immediately after the object is instantiated (created). The term '''constructor''' is standard object-oriented programming terminology, but although it does in <var class="product">SOUL</var>, it does not appear as an actual keyword in most object-oriented programming languages.

	<dt>[[Object variables#Discarding objects\|Discard]]		<dt>[[Object variables#Discarding objects\|Discard]]

JAL: /* See also */

2013-10-14T21:54:37Z

JAL at 21:52, 14 October 2013

2013-10-14T21:52:42Z

← Older revision		Revision as of 21:52, 14 October 2013
Line 83:		Line 83:
	<li>[[Classes and Objects]]		<li>[[Classes and Objects]]
	<li>[[Lists of classes and methods]]		<li>[[Lists of classes and methods]]
	<li>[[:Category:~~Janus SOAP ULI~~ topics\|~~Janus SOAP ULI~~: collected topics]]		<li>[[:Category:SOUL object-oriented programming topics\|SOUL object-oriented programming: collected topics]]
	<li>[[Getting started with object-oriented programming for User Language programmers]]		<li>[[Getting started with object-oriented programming for User Language programmers]]
	</ul>		</ul>

	[[Category:SOUL]]		[[Category:SOUL]]

← Older revision		Revision as of 21:54, 14 October 2013
Line 88:		Line 88:

	[[Category:SOUL]]		[[Category:SOUL]]
			[[Category:SOUL object-oriented programming topics]]