Object Oriented Programming in Script/Object Oriented Programming - Revision history

Andrew Branscom at 16:43, 2 January 2026

2026-01-02T16:43:46Z

← Older revision		Revision as of 12:43, 2 January 2026
Line 115:		Line 115:
	* [[:Category:SCI Documentation\|SCI Documentation]]		* [[:Category:SCI Documentation\|SCI Documentation]]
	* [[:Category:Official SCI Documentation\|Official SCI Documentation]]		* [[:Category:Official SCI Documentation\|Official SCI Documentation]]
	* [[:Category:Scripting ~~Articles~~\|Scripting Articles]]		* [[:Category:Scripting\|Scripting Articles]]
	* [[:Category:Objects\|Objects]]		* [[:Category:Objects\|Objects]]
	* [[Script Resource (SCI)]]		* [[Script Resource (SCI)]]
Line 137:		Line 137:
	[[Category:Official Documentation]]		[[Category:Official Documentation]]
	[[Category:Official SCI Documentation]]		[[Category:Official SCI Documentation]]
	[[Category:Scripting ~~Articles~~]]		[[Category:Scripting]]
	[[Category:SCI Scripting ~~Articles~~]]		[[Category:SCI Scripting]]
	[[Category:Scripting]]		[[Category:Scripting]]
	[[Category:SCI Scripting]]		[[Category:SCI Scripting]]

Andrew Branscom: /* Also See */

2026-01-02T16:42:25Z

Also See

← Older revision		Revision as of 12:42, 2 January 2026
Line 139:		Line 139:
	[[Category:Scripting Articles]]		[[Category:Scripting Articles]]
	[[Category:SCI Scripting Articles]]		[[Category:SCI Scripting Articles]]
	[[Category:Scripting ~~Articles~~]]		[[Category:Scripting]]
	[[Category:SCI Scripting ~~Articles~~]]		[[Category:SCI Scripting]]
	[[Category:Script Resources]]		[[Category:Script Resources]]
	[[Category:SCI Script Resources]]		[[Category:SCI Script Resources]]
	[[Category:Official SCI Documentation]]		[[Category:Official SCI Documentation]]

Andrew Branscom: /* Also See */

2026-01-02T00:26:33Z

Also See

← Older revision		Revision as of 20:26, 1 January 2026
Line 137:		Line 137:
	[[Category:Official Documentation]]		[[Category:Official Documentation]]
	[[Category:Official SCI Documentation]]		[[Category:Official SCI Documentation]]
	[[Category:Scripting]]		[[Category:Scripting Articles]]
	[[Category:SCI Scripting]]		[[Category:SCI Scripting Articles]]
	[[Category:Scripting Articles]]		[[Category:Scripting Articles]]
	[[Category:SCI Scripting Articles]]		[[Category:SCI Scripting Articles]]

Andrew Branscom: /* Also See */

2026-01-02T00:19:51Z

Also See

← Older revision		Revision as of 20:19, 1 January 2026
Line 116:		Line 116:
	* [[:Category:Official SCI Documentation\|Official SCI Documentation]]		* [[:Category:Official SCI Documentation\|Official SCI Documentation]]
	* [[:Category:Scripting Articles\|Scripting Articles]]		* [[:Category:Scripting Articles\|Scripting Articles]]
	* [[:Category:~~Object Pages~~\|~~Object Pages~~]]		* [[:Category:Objects\|Objects]]
	* [[Script Resource (SCI)]]		* [[Script Resource (SCI)]]
	* [[SCI Specifications: Chapter 1 - Introduction#SCRIPT\|SCRIPT in the SCI Specifications]]		* [[SCI Specifications: Chapter 1 - Introduction#SCRIPT\|SCRIPT in the SCI Specifications]]

Andrew Branscom: /* Introduction */

2026-01-02T00:18:41Z

Introduction

← Older revision		Revision as of 20:18, 1 January 2026
Line 18:		Line 18:
	==<br /> Introduction ==		==<br /> Introduction ==

			<blockquote>
	Object oriented programming (OOP) is a relatively new paradigm in programming. The Smalltalk language, developed at Xerox PARC, was the first language to fully use the concept of OOP. Since then, many languages (such as C++, Scheme, Objective C, and Actor) have incorporated the concepts to different degrees. Because of the power of OOP for things such as simulations (and after all, what are adventure games?), Script was designed with the intention that much of the programming would use this concept. Those of us using the language over the last several months have found ourselves moving more and more away from its procedural aspects and toward the OOP aspects -- rooms, dialogs, menus, everything is now an object of one sort or another.		Object oriented programming (OOP) is a relatively new paradigm in programming. The Smalltalk language, developed at Xerox PARC, was the first language to fully use the concept of OOP. Since then, many languages (such as C++, Scheme, Objective C, and Actor) have incorporated the concepts to different degrees. Because of the power of OOP for things such as simulations (and after all, what are adventure games?), Script was designed with the intention that much of the programming would use this concept. Those of us using the language over the last several months have found ourselves moving more and more away from its procedural aspects and toward the OOP aspects -- rooms, dialogs, menus, everything is now an object of one sort or another.

Line 104:		Line 105:

	Rather than continuing to give examples in an unspecified language, we will first define the terms to be used in discussions of OOP languages and then give the syntax and commands which Script uses. Following that will be more examples of the use of OOP in adventure game coding.		Rather than continuing to give examples in an unspecified language, we will first define the terms to be used in discussions of OOP languages and then give the syntax and commands which Script uses. Following that will be more examples of the use of OOP in adventure game coding.
			</blockquote>

	==<br /> References ==		==<br /> References ==

Andrew Branscom at 00:09, 2 January 2026

2026-01-02T00:09:48Z

← Older revision		Revision as of 20:09, 1 January 2026
Line 1:		Line 1:
			[[Category:SCI Pages]]
	[[Official SCI Documentation]]<br />		[[Official SCI Documentation]]<br />
			[[Object Oriented Programming in Script\|Table of Contents]]

	<div align="center">		<div align="center">
	Chapter:		Chapter:
Line 10:		Line 12:
	[[Object Oriented Programming in Script/An Extended Example\|6]] \|		[[Object Oriented Programming in Script/An Extended Example\|6]] \|
	[[Object Oriented Programming in Script/Index\|Index]]		[[Object Oriented Programming in Script/Index\|Index]]
	</div~~><br /~~>		</div>
			<div align="center"><span style="font-size: 22pt">Object Oriented Programming</span><br />''Author: [[Jeff Stephenson]]''<br />''1988-04-04''</div></div>
	<div align="center"><span style="font-size: 22pt">Object Oriented Programming</span><br />
	''Author: [[Jeff Stephenson]]''<br />
	''~~Date: 4 April~~ 1988''</div>

	~~ ~~		<br />
			==<br /> Introduction ==

	Object oriented programming (OOP) is a relatively new paradigm in programming. The Smalltalk language, developed at Xerox PARC, was the first language to fully use the concept of OOP. Since then, many languages (such as C++, Scheme, Objective C, and Actor) have incorporated the concepts to different degrees. Because of the power of OOP for things such as simulations (and after all, what are adventure games?), Script was designed with the intention that much of the programming would use this concept. Those of us using the language over the last several months have found ourselves moving more and more away from its procedural aspects and toward the OOP aspects -- rooms, dialogs, menus, everything is now an object of one sort or another.		Object oriented programming (OOP) is a relatively new paradigm in programming. The Smalltalk language, developed at Xerox PARC, was the first language to fully use the concept of OOP. Since then, many languages (such as C++, Scheme, Objective C, and Actor) have incorporated the concepts to different degrees. Because of the power of OOP for things such as simulations (and after all, what are adventure games?), Script was designed with the intention that much of the programming would use this concept. Those of us using the language over the last several months have found ourselves moving more and more away from its procedural aspects and toward the OOP aspects -- rooms, dialogs, menus, everything is now an object of one sort or another.
Line 105:		Line 105:
	Rather than continuing to give examples in an unspecified language, we will first define the terms to be used in discussions of OOP languages and then give the syntax and commands which Script uses. Following that will be more examples of the use of OOP in adventure game coding.		Rather than continuing to give examples in an unspecified language, we will first define the terms to be used in discussions of OOP languages and then give the syntax and commands which Script uses. Following that will be more examples of the use of OOP in adventure game coding.

	~~ ~~		==<br /> References ==

			<references /><!-- Do not edit this section. It is autopopulated by <ref></ref> tags -->

	~~;Notes~~		==<br /> Also See ==
	<~~references~~ />

			* [[:Category:SCI Documentation\|SCI Documentation]]
			* [[:Category:Official SCI Documentation\|Official SCI Documentation]]
			* [[:Category:Scripting Articles\|Scripting Articles]]
			* [[:Category:Object Pages\|Object Pages]]
			* [[Script Resource (SCI)]]
			* [[SCI Specifications: Chapter 1 - Introduction#SCRIPT\|SCRIPT in the SCI Specifications]]


	[[Object Oriented Programming in Script \| Table of Contents]]		[[Official SCI Documentation]]<br />
			[[Object Oriented Programming in Script\|Table of Contents]]
	~~ ~~

	<span style="float: left">[[Object Oriented Programming in Script \|< Previous: Table of Contents]]</span>		<span style="float: left">[[Object Oriented Programming in Script \|< Previous: Table of Contents]]</span>
	<span style="float: right">[[Object Oriented Programming in Script/Object Oriented Terminology\|Next: Object Oriented Terminology >]]</span>		<span style="float: right">[[Object Oriented Programming in Script/Object Oriented Terminology\|Next: Object Oriented Terminology >]]</span>


			[[Category:References]]
			[[Category:SCI References]]
			[[Category:Historical Pages]]
			[[Category:SCI Historical Pages]]
			[[Category:Development]]
			[[Category:SCI Development]]
			[[Category:Documentation]]
	[[Category:SCI Documentation]]		[[Category:SCI Documentation]]
			[[Category:Official Documentation]]
			[[Category:Official SCI Documentation]]
	[[Category:Scripting]]		[[Category:Scripting]]
			[[Category:SCI Scripting]]
			[[Category:Scripting Articles]]
			[[Category:SCI Scripting Articles]]
			[[Category:Script Resources]]
			[[Category:SCI Script Resources]]
			[[Category:Official SCI Documentation]]

Andrew Branscom: 2 revisions imported

2025-02-16T20:49:34Z

2 revisions imported

← Older revision	Revision as of 16:49, 16 February 2025
(No difference)

Andrew Branscom: 1 revision imported

2024-06-03T05:11:15Z

1 revision imported

← Older revision	Revision as of 01:11, 3 June 2024
(No difference)

sierraw>Andrew Branscom: 1 revision imported

2018-03-02T23:12:21Z

1 revision imported

New page

[[Official SCI Documentation]]<br />

<div align="center">
Chapter:
[[Object Oriented Programming in Script/Object Oriented Programming|1]] |
[[Object Oriented Programming in Script/Object Oriented Terminology|2]] |
[[Object Oriented Programming in Script/Classes|3]] |
[[Object Oriented Programming in Script/Objects|4]] |
[[Object Oriented Programming in Script/Sending Messages|5]] |
[[Object Oriented Programming in Script/An Extended Example|6]] |
[[Object Oriented Programming in Script/Index|Index]]
</div><br />

<div align="center"><span style="font-size: 22pt">Object Oriented Programming</span><br />
''Author: [[Jeff Stephenson]]''<br />
''Date: 4 April 1988''</div>

 

Object oriented programming (OOP) is a relatively new paradigm in programming. The Smalltalk language, developed at Xerox PARC, was the first language to fully use the concept of OOP. Since then, many languages (such as C++, Scheme, Objective C, and Actor) have incorporated the concepts to different degrees. Because of the power of OOP for things such as simulations (and after all, what are adventure games?), Script was designed with the intention that much of the programming would use this concept. Those of us using the language over the last several months have found ourselves moving more and more away from its procedural aspects and toward the OOP aspects -- rooms, dialogs, menus, everything is now an object of one sort or another.

OOP languages basically turn the data/procedure relationship in conventional programming inside out: instead of sending data to a procedure for the procedure to act upon, we send a message to data (an object) telling it what to do. This allows the sender of the message to obtain a service
from the receiver object with no knowledge of how this service is performed, something which is not possible in procedural languages.

As an example, consider displaying the 'value' of data elements in a program in a procedural language and then an OOP language. In this example, we'll assume that the procedural language is untyped (as opposed to the current direction of strong typing in C, Ada, Pascal, etc.). Strong typing would make the follow exercise even harder. To make the example more concrete, we'll imagine that we want to be able to display one of two data element types: a list of strings or an array of integers.

Procedurally, we'll use a C-like language (with lots of extensions which don't exist in C) and write

<blockquote>
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">
Show(data)
/* Here's one place C would have a problem -- data could either be
* a list of strings or an array of integers. What type does one
* declare?
*/
{
switch (typeof(data)) { /* how is typeof() implemented? */
case stringList:
for (str = ListStart(data) ;
str != NULL ;
str = ListNext(data)
)
printf(str);
break;
case integerArray:
for (i = 0 ; i < sizeof(data) ; ++i)
printf("%d", data[i]);
break;
}
}
</syntaxhighlight>
</blockquote>

Note that one could not easily write this in C because of strong data typing and the difficulty of implementing both typeof() and this particular use of sizeof(). What usually ends up happening in a procedural language is that instead of one general-purpose Show() procedure, one writes a lot of special purpose ShowStringList() and ShowIntegerArray() procedures and whoever wants to display something has to be aware of the type of data being displayed and call the appropriate procedure.

Contrast this with object-oriented programming. Either type of data can be displayed by simply sending the data object the show message:

<blockquote>
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">
(data show:)
</syntaxhighlight>
</blockquote>

Since both Arrays and Lists are sub-types of the Collection type they implement this in the same way (they actually share the code):

<blockquote>
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">
(method (show)
(self eachElementDo: #show:)
)
</syntaxhighlight>
</blockquote>

Both the list and the array simple send each of their elements the message requesting the element to display itself. The elements, strings and integers, implement the show method in different manners. The show method for a string might be

<blockquote>
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">

(method (show)
(Print str)
)
</syntaxhighlight>
</blockquote>

whereas that for the integer might be

<blockquote>
<div class="CodeBlockHeader">Code:</div>
<syntaxhighlight lang="sci">
(method (show)
(Print "%d" number)
)
</syntaxhighlight>
</blockquote>

Note how much simpler the OOP code is than the procedural code. This is because the responsibility for displaying something is delegated to the object being displayed, freeing the calling code from knowing anything about it. In fact, because of this passing on of responsibility, the above code will also handle lists which contain elements of several data types -- (data show:) would also work if data were a list which contained a string, an integer, a list of integers, an array of strings, and a list of arrays of lists of strings. No change in code is necessary.

Another benefit of the OOP code is that adding a new data type is as easy as writing the show method for the data type. In the procedural code, the Show() procedure would need re-writing, as would the typeof() and sizeof() procedures -- the addition of the new type propagates throughout the code rather than remaining isolated in the new type.

Rather than continuing to give examples in an unspecified language, we will first define the terms to be used in discussions of OOP languages and then give the syntax and commands which Script uses. Following that will be more examples of the use of OOP in adventure game coding.

 

;Notes
<references />

 

[[Object Oriented Programming in Script | Table of Contents]]

 

<span style="float: left">[[Object Oriented Programming in Script |< Previous: Table of Contents]]</span>
<span style="float: right">[[Object Oriented Programming in Script/Object Oriented Terminology|Next: Object Oriented Terminology >]]</span>

 

[[Category:SCI Documentation]]
[[Category:Scripting]]

← Older revision		Revision as of 20:19, 1 January 2026
Line 116:		Line 116:
	* [[:Category:Official SCI Documentation\|Official SCI Documentation]]		* [[:Category:Official SCI Documentation\|Official SCI Documentation]]
	* [[:Category:Scripting Articles\|Scripting Articles]]		* [[:Category:Scripting Articles\|Scripting Articles]]
	* [[:Category:~~Object Pages~~\|~~Object Pages~~]]		* [[:Category:Objects\|Objects]]
	* [[Script Resource (SCI)]]		* [[Script Resource (SCI)]]
	* [[SCI Specifications: Chapter 1 - Introduction#SCRIPT\|SCRIPT in the SCI Specifications]]		* [[SCI Specifications: Chapter 1 - Introduction#SCRIPT\|SCRIPT in the SCI Specifications]]