Smalltalk80LanguageImplementation:Chapter 16 - Revision history

Onionmixer: 오타 및 오류수정

2015-07-12T13:48:06Z

오타 및 오류수정

← Older revision		Revision as of 13:48, 12 July 2015
Line 193:		Line 193:


	❏ Behavior's Creating Protocol The methods in a class description are stored in a dictionary we refer to as the method dictionary. It is also sometimes called a message dictionary. The keys in this dictionary are message selectors; the values are the compiled form of methods (instances of CompiledMethod). The protocol for creating the method dictionary supports compiling methods as well as adding the association between a selector and a compiled method. It also supports accessing both the compiled and noncompiled (source) versions of the method.
			❏ Behavior's Creating Protocol


			The methods in a class description are stored in a dictionary we refer to as the method dictionary. It is also sometimes called a message dictionary. The keys in this dictionary are message selectors; the values are the compiled form of methods (instances of CompiledMethod). The protocol for creating the method dictionary supports compiling methods as well as adding the association between a selector and a compiled method. It also supports accessing both the compiled and noncompiled (source) versions of the method.

	{\| style="border: 1px solid black;"		{\| style="border: 1px solid black;"
Line 269:		Line 273:


	❏ Behavior's Accessing Protocol The messages that access the contents of a method dictionary distinguish among the selectors in the class's locally specified method dictionary, and those in the method dictionaries of the class and each of its superclasses.
			❏ Behavior's Accessing Protocol


			The messages that access the contents of a method dictionary distinguish among the selectors in the class's locally specified method dictionary, and those in the method dictionaries of the class and each of its superclasses.

	{\| style="border: 1px solid black;"		{\| style="border: 1px solid black;"
Line 336:		Line 344:
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	\|String allClassVarNames\|\|Set (StringBlter DependentsFields ErrorRecursion)		\|String allClassVarNames\|\|Set (StringBlter DependentsFields ErrorRecursion)
			\|- style="vertical-align:top;"
			\|Text sharedPools\|\|a Set containing one element, TextConstants, a Dictionary
	\|}		\|}


	~~Text sharedPools\|\|a Set containing one element, TextConstants, a Dictionary~~
	The accessing protocol includes messages for obtaining collections of the superclasses and subclasses of a class. These messages distinguish between a class's immediate superclass and subclasses, and all classes in the class's superclass chain.		The accessing protocol includes messages for obtaining collections of the superclasses and subclasses of a class. These messages distinguish between a class's immediate superclass and subclasses, and all classes in the class's superclass chain.

Line 354:		Line 364:
	\|superclass\|\|Answer the receiver's immediate superclass.		\|superclass\|\|Answer the receiver's immediate superclass.
	\|- style="color: black; background-color: gray;"		\|- style="color: black; background-color: gray;"
			\|- style="vertical-align:top;"
			\|allSuperclasses\|\|Answer an OrderedCollection of the receiver's superclass and the receiver's ancestor's superclasses. The first element is the receiver's immediate superclass, followed by its superclass, and so on; the last element is always Object.
	\| colspan="2" \|Behavior instance protocol		\| colspan="2" \|Behavior instance protocol
	\|}		\|}


	allSuperclasses\|\|Answer an OrderedCollection of the receiver's superclass and the receiver's ancestor's superclasses. The first element is the receiver's immediate superclass, followed by its superclass, and so on; the last element is always Object.
	Thus for example		Thus for example

Line 379:		Line 390:


	❏ Behavior's Testing Protocol Testing protocol provides the messages needed to find out information about the structure of a class and the form of its instances. The structure of a class consists of its relationship to other classes, its ability to respond to messages, the class in which a message is specified, and so on.
			❏ Behavior's Testing Protocol


			Testing protocol provides the messages needed to find out information about the structure of a class and the form of its instances. The structure of a class consists of its relationship to other classes, its ability to respond to messages, the class in which a message is specified, and so on.


Line 510:		Line 525:


	❏ Behavior's Enumerating Protocol Messages specified in class Behavior also support listing out particular sets of objects associated with a class and applying each as the argument of a block. This enumeration of objects is similar to that provided in the collection classes, and consists of enumerating over all subclasses, superclasses, instances, and instances of subclasses. In addition, two messages support selecting those subclasses or superclasses for which a block evaluates to true.
			❏ Behavior's Enumerating Protocol


			Messages specified in class Behavior also support listing out particular sets of objects associated with a class and applying each as the argument of a block. This enumeration of objects is similar to that provided in the collection classes, and consists of enumerating over all subclasses, superclasses, instances, and instances of subclasses. In addition, two messages support selecting those subclasses or superclasses for which a block evaluates to true.

	{\| style="border: 1px solid black;"		{\| style="border: 1px solid black;"
Line 635:		Line 654:
	\|removeInstVarName: aString\|\|Remove the argument, aString, as one of the receiver's instance variables. Report an error if aString is not found.		\|removeInstVarName: aString\|\|Remove the argument, aString, as one of the receiver's instance variables. Report an error if aString is not found.
	\|- style="color: black; background-color: gray;"		\|- style="color: black; background-color: gray;"
	\| colspan="2" \|~~Class Description~~ instance protocol		\| colspan="2" \|ClassDescription instance protocol
	\|}		\|}

Line 656:		Line 675:
	\|whichCategoryIncludesSelector: selector\|\|Answer the category of the argument, selector, in the organization of the receiver's method dictionary, or answer nil if the selector can not be found.		\|whichCategoryIncludesSelector: selector\|\|Answer the category of the argument, selector, in the organization of the receiver's method dictionary, or answer nil if the selector can not be found.
	\|- style="color: black; background-color: gray;"		\|- style="color: black; background-color: gray;"
	\| colspan="2" \|~~Class Description~~ instance protocol		\| colspan="2" \|ClassDescription instance protocol
	\|}		\|}

Onionmixer: 정오표 수정

2014-05-09T09:34:07Z

정오표 수정

← Older revision		Revision as of 09:34, 9 May 2014
Line 106:		Line 106:


	We have now introduced the protocol for most of the classes that ~~de' scribe~~ the basic components of the Smalltalk-80 system. One notable exception is the protocol for the classes themselves. Four classes--Behavior, ClassDescription, Metaclass, and Class~interact to provide; the facilities needed to describe new classes. Creating a new class involves compiling methods and specifying names for instance variables, class variables, pool variables, and the class itself.		We have now introduced the protocol for most of the classes that describe the basic components of the Smalltalk-80 system. One notable exception is the protocol for the classes themselves. Four classes--Behavior, ClassDescription, Metaclass, and Class--interact to provide; the facilities needed to describe new classes. Creating a new class involves compiling methods and specifying names for instance variables, class variables, pool variables, and the class itself.


Line 486:		Line 486:
	\|inheritsFrom: aClass\|\|Answer whether the argument, aClass, is on the receiver's superclass chain.		\|inheritsFrom: aClass\|\|Answer whether the argument, aClass, is on the receiver's superclass chain.
	\|- style="vertical-align:top;"		\|- style="vertical-align:top;"
	\|kindOfSubclass\|\|Answer a String that is the keyword that describes the receiver as a class: either a regular (fixed length) subclass, a ~~variableSubctass~~, a variableByteSubclass, or a variableWordSubclass.		\|kindOfSubclass\|\|Answer a String that is the keyword that describes the receiver as a class: either a regular (fixed length) subclass, a variableSubclass, a variableByteSubclass, or a variableWordSubclass.
	\|- style="color: black; background-color: gray;"		\|- style="color: black; background-color: gray;"
	\| colspan="2" \|Behavior instance protocol		\| colspan="2" \|Behavior instance protocol
Line 639:		Line 639:


	ClassDescription was provided as a common superclass for Class and ~~Metactass~~ in order to provide further structuring to the description of a class. This helps support a general program development environment. Specifically, ClassDescription adds structure for organizing the selector/method pairs of the method dictionary. This organization is a simple categorization scheme by which the subsets of the dictionary are grouped and named, precisely the way we have been grouping and naming messages throughout the chapters of this book. ClassDescriPtion also provides the mechanisms for storing a full class description on an external stream (a file), and the mechanisms by which any changes to the class description are logged.		ClassDescription was provided as a common superclass for Class and Metaclass in order to provide further structuring to the description of a class. This helps support a general program development environment. Specifically, ClassDescription adds structure for organizing the selector/method pairs of the method dictionary. This organization is a simple categorization scheme by which the subsets of the dictionary are grouped and named, precisely the way we have been grouping and naming messages throughout the chapters of this book. ClassDescriPtion also provides the mechanisms for storing a full class description on an external stream (a file), and the mechanisms by which any changes to the class description are logged.


Line 698:		Line 698:
	<syntaxhighlight lang="smalltalk">		<syntaxhighlight lang="smalltalk">
	LinkedList superclass		LinkedList superclass
	subclass: #~~AudioTrail~~		subclass: #AuditTrail
	instanceVariableNames: LinkedList instanceVariableString		instanceVariableNames: LinkedList instanceVariableString
	classVariableNames: LinkedList classVariableString		classVariableNames: LinkedList classVariableString
Line 717:		Line 717:


	~~AuditTraii~~ declared two instance variable names, firstLink and lastLink, and copied messages first, last, size, isEmpty, add:, addFirst:, and addLast:. We also copied all the messages in the category private on the assumption that at least one of them is needed in the implementation of the external messages.		AuditTrail declared two instance variable names, firstLink and lastLink, and copied messages first, last, size, isEmpty, add:, addFirst:, and addLast:. We also copied all the messages in the category private on the assumption that at least one of them is needed in the implementation of the external messages.

Onionmixer: SMALLTALK80 Chapter 16 Protocol for Classes 페이지 추가

2014-04-23T14:15:17Z

SMALLTALK80 Chapter 16 Protocol for Classes 페이지 추가

Show changes