Smalltalk Syntax Cheat Sheet - Versionsgeschichte

Cg: /* Smalltalk Philosophy */

2026-06-07T07:15:16Z

Smalltalk Philosophy

← Nächstältere Version		Version vom 7. Juni 2026, 07:15 Uhr
Zeile 5:		Zeile 5:

	== Smalltalk Philosophy ==		== Smalltalk Philosophy ==

			A very short summary and introduction to the fundamental principles underlying the Smalltalk language.

	* Everything is an '''Object'''<br>this includes the most basic ''things'' like numbers, strings and characters, up to complex objects like windows, editors, compilers, applications etc.		* Everything is an '''Object'''<br>this includes the most basic ''things'' like numbers, strings and characters, up to complex objects like windows, editors, compilers, applications etc.
Zeile 45:		Zeile 47:
	: blocks can receive messages, especially loop messages: "<code>[ a < 10] whileTrue:[ Transcript showCR: a. a := a + 1 ]</code>",		: blocks can receive messages, especially loop messages: "<code>[ a < 10] whileTrue:[ Transcript showCR: a. a := a + 1 ]</code>",
	: and they can be returned from a method (''answer from a message'') .		: and they can be returned from a method (''answer from a message'') .

			* a small language and a big library<br>the syntax of Smalltalk is tiny and learned in minutes. The library (i.e. the classes you get) is big, flexible and extendable. The IDE is really an "''integrated environment''" as it is both completely implemented in Smalltalk, part of the running system (not outside), immediately updating the running system.

	== Syntax ==		== Syntax ==

Cg: /* Smalltalk Philosophy */

2026-06-07T07:10:46Z

Smalltalk Philosophy

@@ Zeile 6: / Zeile 6: @@
 == Smalltalk Philosophy ==
 * Messages without argument are called "''unary messages''"; those with arguments are called "''keyword messages''"
-: For example "<code>Transcript clear</code>" (sends the message "clear" to the Transcript object),
+: For example "<code>Transcript clear</code>" sends the message "clear" to the Transcript object; a unary message,
-: and "<code>Transcript show: 'hello'</code>" (sends the message "show:" to the Transcript, passing a string argument),
+: and "<code>Transcript show:'hello'</code>" sends the message "show:" to the Transcript, passing a string argument; a keyword message
 * To allow for arithmetic operations, any non-letter character (except for a few) are treated like a message name and written between the receiver and the one and only argument. These are called "''binary messages''".
-: For example: <code>"3 + 4"</code> or <code>"abc , def"</code> (yes, the comma is an operator; it does string concatenation)
+: For example: <code>"3+4"</code> or <code>"abc,def"</code> (yes, the comma is an operator; it does string concatenation).<br>You can place whitespace anywhere between selectors, keywords and arguemnts (eg. <code>"3 + 4"</code> and <code>"3+4"</code> are the same).
-* The object my respond (or "answer") by returning some result object. In the above example, "<code>3+4</code>" would answer "7", and "<code>'hello' , 'world'</code>" would answer 'helloworld'
+* An object may respond (or "''answer''") by returning a result object. In the above example, "<code>3+4</code>" would answer "7", and "<code>'hello' , 'world'</code>" would answer 'helloworld'
 * Class can inherit common functionality (i.e. method implementations) from a superclass. Thus creating a hierarchy of classes. Typical hierarchies are the Number hierarchy, Collections, Streams and UI Widgets.
 == Syntax ==

Cg: /* Numbers */

2026-06-07T06:25:36Z

Numbers

← Nächstältere Version		Version vom 7. Juni 2026, 06:25 Uhr
Zeile 99:		Zeile 99:
	\|-		\|-
	\| Fractions		\| Fractions
	\| <code>(1/3)</code><br><code>(17/2)</code>		\| <code>(1/3)</code><br><code>(17/2)</code><br>(-3/2)
	\|		\|
	\|-		\|-
Zeile 105:		Zeile 105:
	\| <code>1234.53s2</code>		\| <code>1234.53s2</code>
	\| ''the number after the s specifies the number of digits''		\| ''the number after the s specifies the number of digits''
			\|-
			\| Complex
			\| <code>(1.5 + 3i)</code><br><code>2i</code><br><code>(3.0q + 5.0qi</code>)
	\|}		\|}

Cg: /* Numbers */

2026-06-07T06:22:47Z

Numbers

← Nächstältere Version		Version vom 7. Juni 2026, 06:22 Uhr
Zeile 104:		Zeile 104:
	\| ScaledDecimals		\| ScaledDecimals
	\| <code>1234.53s2</code>		\| <code>1234.53s2</code>
	\| the number after the s specifies the number of digits		\| ''the number after the s specifies the number of digits''
	\|}		\|}

Cg: /* Comments */

2026-06-07T06:22:05Z

Comments

← Nächstältere Version		Version vom 7. Juni 2026, 06:22 Uhr
Zeile 515:		Zeile 515:
	=== Comments ===		=== Comments ===
	* "/<br>End of line comment		* "/<br>End of line comment
	* "<<X<br> ... <br>X<br>token delimited comment		* "<<X<br> ... <br>X<br>token delimited comment;<br>X can be any word and a line starting with X ends the comment

	=== String Literals ===		=== String Literals ===

Cg: /* Smalltalk/X Language Extensions */

2026-06-07T06:20:38Z

Smalltalk/X Language Extensions

← Nächstältere Version		Version vom 7. Juni 2026, 06:20 Uhr
Zeile 509:		Zeile 509:
	* { expr1 . expr2 . ... }<br>Brace Array Construction<br>Each expression is evaluated (left to right), and an Array with the results is created at execution time.<br>Notice that separating full stops are required, as opposed to constant literal arrays, where elements are separated by spaces. The generated Array is mutable (can be modified), whereas a constant array is not.		* { expr1 . expr2 . ... }<br>Brace Array Construction<br>Each expression is evaluated (left to right), and an Array with the results is created at execution time.<br>Notice that separating full stops are required, as opposed to constant literal arrays, where elements are separated by spaces. The generated Array is mutable (can be modified), whereas a constant array is not.

	== Smalltalk/X Language Extensions ==		== Summary of Smalltalk/X Language Extensions ==

	These are ST/X specific, and not (as of 2026) implemented in other Smalltalk systems.		These are ST/X specific, and not (as of 2026) implemented in other Smalltalk systems.

			=== Comments ===
			* "/<br>End of line comment
			* "<<X<br> ... <br>X<br>token delimited comment

	=== String Literals ===		=== String Literals ===

Cg: /* Characters and Strings */

2026-06-07T06:18:25Z

Characters and Strings

Cg: /* Numbers */

2026-06-07T06:15:35Z

Numbers

← Nächstältere Version		Version vom 7. Juni 2026, 06:15 Uhr
Zeile 76:		Zeile 76:
	\| Floats<br>(IEEE double; roughly 17 digits)		\| Floats<br>(IEEE double; roughly 17 digits)
	\| 12.456<br>1.234e17<br>-6.9<br>-6e-10<br>Float pi<br>Float e		\| 12.456<br>1.234e17<br>-6.9<br>-6e-10<br>Float pi<br>Float e
	\| ''called "Float", but actually hold double precision''<br>Common constants can be referred to "by name".		\| ''called "Float", but actually hold double precision<br>Common constants can be referred to "by name".''
	\|-		\|-
	\| Short floats<br>(IEEE single; roughly 8 digits) (*)		\| Short floats<br>(IEEE single; roughly 8 digits) (*)
	\| <code>1.~~234f17~~</code><br><code>-6f-10</code>		\| <code>1.234e17f</code><br><code>-6e-10f</code>
	\| this is controlled by a ParserFlag (singlePrecisionFloatF), which is currently defaulted to false. Thus, by default, double precision floats are created with the 'f' exponent character.		\| <strike>''this is controlled by a ParserFlag (singlePrecisionFloatF), which is currently defaulted to false. Thus, by default, double precision floats are created with the 'f' exponent character.''</strike>
	\|-		\|-
	\| Long floats<br>(IEEE ~~quad~~; roughly 20 digits) (*)		\| Long floats<br>(IEEE extended; roughly 20 digits) (*)
	\| <code>1.~~234q17~~</code><br><code>-6q-10</code>		\| <code>1.234e17q</code><br><code>-6q-10q</code>
	\| ''actual precision depends on the underlying CPU<br>(on x86/x86_64: ~~only~~ 80bit)		\| ''actual precision depends on the underlying CPU<br>(x86/x86_64: 80bit; Sparc: 128 bit)
	\|-		\|-
	\| Quad floats;<br>roughly 34 digits (*)		\| Quad floats;<br>(IEEE quad; roughly 34 digits (*)
	\| <code>1.~~234Q17~~</code><br><code>-6Q-10</code>		\| <code>1.234e17Q</code><br><code>-6e-10Q</code>
	\| ''computed in software; therefore slower; this is not yet officially released.		\| ''computed in software; therefore slower; <strike>this is not yet officially released.</strike>
	\|-		\|-
	\| ~~Large~~ floats;<br>roughly 60 digits (*)		\| Octuple floats;<br>roughly 60 digits (*)
	\| <code>1.~~234QL17~~</code><br><code>-~~6QL~~-10</code>		\| <code>1.234e17QO</code><br><code>-6e-10QP</code>
	\| ''computed in software; therefore slower; this is not yet officially released.		\| ''computed in software; therefore slower; <strike>this is not yet officially released.</strike>
			\|-
			\| Large floats;<br>roughly 60 digits by default, but any precision possible (*)
			\| <code>1.234e17QL</code><br><code>-6e-10QL</code>
			\| ''computed in software; therefore slower; <strike>this is not yet officially released.</strike>
	\|-		\|-
	\| Fractions		\| Fractions

Cg: /* Characters and Strings */

2026-06-07T06:06:56Z

Characters and Strings

← Nächstältere Version		Version vom 7. Juni 2026, 06:06 Uhr
Zeile 119:		Zeile 119:
	\| supports the common escape sequences, such as "\n", "\t", "\xHH", "\uXXXX"		\| supports the common escape sequences, such as "\n", "\t", "\xHH", "\uXXXX"
	\|-		\|-
	\| Strings<br>(~~With~~ ~~Embedded~~ ~~Expressios~~) (*)		\| Strings<br>(with embedded expressios) (*)
	\| <code>e'hello {OperatingSystem getLoginName}'</code>		\| <code>e'hello {OperatingSystem getLoginName}'</code>
	\| expanded strings <br>expressions in braces are evaluated at runtime and sliced into the string (also a C-string). Similar to python's f-strings.		\| expanded strings <br>expressions in braces are evaluated at runtime and sliced into the string (also a C-string). Similar to python's f-strings.
	\|-		\|-
	\| Strings<br>(~~Language~~ translated with ~~Embedded~~ ~~Expressios~~) (*)		\| Strings<br>(national language translated with embedded expressios) (*)
	\| <code>i'hello {OperatingSystem getLoginName}'</code>		\| <code>i'hello {OperatingSystem getLoginName}'</code>
	\| international strings<br>like above, but the string is also possibly translated to a national language		\| international strings<br>like above, but the string is also possibly translated to a national language

Cg: /* Characters and Strings */

2026-06-07T06:05:48Z

Characters and Strings

← Nächstältere Version		Version vom 7. Juni 2026, 06:05 Uhr
Zeile 109:		Zeile 109:
	\| Characters		\| Characters
	\| <code>$a</code><br><code>Character space</code><br><code>Character nl</code><br>Also: "<code>null</code>", "<code>tab</code>", "<code>return</code>", "<code>bell</code>"...<br>Or:<br><code>Character codePoint:n</code>		\| <code>$a</code><br><code>Character space</code><br><code>Character nl</code><br>Also: "<code>null</code>", "<code>tab</code>", "<code>return</code>", "<code>bell</code>"...<br>Or:<br><code>Character codePoint:n</code>
	\| ~~''traditionally,~~ Smalltalk does not support any escape sequence''<br>Common constants can be referred to "by name".		\| Smalltalk does not support any escape sequence<br>Common constants can be referred to "''by name''".
	\|-		\|-
	\| Strings		\| Strings
	\| <code>'hello'</code>		\| <code>'hello'</code>
	\| ''traditionally, Smalltalk does not support any escape sequence inside''<br>(I.e. they are what Python calls ''Raw Strings'')<br>But see below...		\| traditionally, Smalltalk does not support any escape sequence inside<br>(i.e. they are what Python calls "''Raw Strings''")<br>But see below...
	\|-		\|-
	\| Strings<br>(C Style) (*)		\| Strings<br>(C Style) (*)
	\| <code>c'hello\nworld'</code>		\| <code>c'hello\nworld'</code>
	\| ''supports the common escape sequences, such as "\n", "\t", "\xHH" ''		\| supports the common escape sequences, such as "\n", "\t", "\xHH", "\uXXXX"
	\|-		\|-
	\| Strings<br>(With Embedded Expressios) (*)		\| Strings<br>(With Embedded Expressios) (*)
	\| <code>e'hello {OperatingSystem getLoginName}'</code>		\| <code>e'hello {OperatingSystem getLoginName}'</code>
	\| ''expressions in braces are evaluated at runtime and sliced into the string (also a C-string)''. Similar to python's f-strings.		\| expanded strings <br>expressions in braces are evaluated at runtime and sliced into the string (also a C-string). Similar to python's f-strings.
	\|-		\|-
	\| Strings<br>(Language translated with Embedded Expressios) (*)		\| Strings<br>(Language translated with Embedded Expressios) (*)
	\| <code>i'hello {OperatingSystem getLoginName}'</code>		\| <code>i'hello {OperatingSystem getLoginName}'</code>
	\| ''like above, but the string is also possibly translated to a national language''		\| international strings<br>like above, but the string is also possibly translated to a national language
	\|-		\|-
	\| Symbols		\| Symbols
	\| <code>#'hello'</code><br><code>#foo</code>		\| <code>#'hello'</code><br><code>#foo</code><br><code>#+</code>
	\| without quotes, if only alphaNumeric characters		\| symbols are interned strings; two symbols with the same characters are guaranteed to be the identical object (not just equal)<br>without quotes, if only alphaNumeric characters
	\|}		\|}

← Nächstältere Version		Version vom 7. Juni 2026, 06:18 Uhr
Zeile 113:		Zeile 113:
	\| Characters		\| Characters
	\| <code>$a</code><br><code>Character space</code><br><code>Character nl</code><br>Also: "<code>null</code>", "<code>tab</code>", "<code>return</code>", "<code>bell</code>"...<br>Or:<br><code>Character codePoint:n</code>		\| <code>$a</code><br><code>Character space</code><br><code>Character nl</code><br>Also: "<code>null</code>", "<code>tab</code>", "<code>return</code>", "<code>bell</code>"...<br>Or:<br><code>Character codePoint:n</code>
	\| Smalltalk does not support any escape sequence<br>Common constants can be referred to "''by name''".		\| ''Smalltalk does not support any escape sequence<br>Common constants can be referred to "by name".''
	\|-		\|-
	\| Strings		\| Strings
	\| <code>'hello'</code>		\| <code>'hello'</code>
	\| traditionally, Smalltalk does not support any escape sequence inside<br>(i.e. they are what Python calls "''Raw Strings''")<br>But see below...		\| ''traditionally, Smalltalk does not support any escape sequence inside<br>(i.e. they are what Python calls "Raw Strings")<br>But see below...''
	\|-		\|-
	\| Strings<br>(C Style) (*)		\| Strings<br>(C Style) (*)
	\| <code>c'hello\nworld'</code>		\| <code>c'hello\nworld'</code>
	\| supports the common escape sequences, such as "\n", "\t", "\xHH", "\uXXXX"		\| ''supports the common C-escape sequences, such as "\n", "\t", "\xHH", "\uXXXX"''
	\|-		\|-
	\| Strings<br>(with embedded expressios) (*)		\| Strings<br>(with embedded expressios) (*)
	\| <code>e'hello {OperatingSystem getLoginName}'</code>		\| <code>e'hello {OperatingSystem getLoginName}'</code>
	\| expanded strings <br>expressions in braces are evaluated at runtime and sliced into the string (also a C-string). Similar to python's f-strings.		\| ''expanded expression strings <br>expressions in braces are evaluated at runtime and sliced into the string (also a C-string). Similar to python's f-strings.''
	\|-		\|-
	\| Strings<br>(national language translated with embedded expressios) (*)		\| Strings<br>(national language translated with embedded expressios) (*)
	\| <code>i'hello {OperatingSystem getLoginName}'</code>		\| <code>i'hello {OperatingSystem getLoginName}'</code>
	\| international strings<br>like above, but the string is also possibly translated to a national language		\| ''international strings<br>like above, but the string is also possibly translated to a national language''
	\|-		\|-
	\| Symbols		\| Symbols
	\| <code>#'hello'</code><br><code>#foo</code><br><code>#+</code>		\| <code>#'hello'</code><br><code>#foo</code><br><code>#+</code>
	\| symbols are interned strings; two symbols with the same characters are guaranteed to be the identical object (not just equal)<br>without quotes, if only alphaNumeric characters		\| ''symbols are interned strings; two symbols with the same characters are guaranteed to be the identical object (not just equal)<br>without quotes, if only alphaNumeric characters''
	\|}		\|}