You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In sec 2.7, we introduce our typographic convention:
A typographic convention. Smalltalkers frequently use the notation “>>” to identify the class to which a method belongs, so, for example, the cellsPerSide method in class SBEGame would be referred to as SBEGame>>cellsPerSide. To indicate that this is not Smalltalk syntax, we will use the special symbol » instead, so this method will appear in the text as SBEGame»cellsPerSide. From now on, when we show a method in this book, we will write the name of the method in this form. Of course, when you actually type the code into the browser, you don’t have to type the class name or the »; instead, you just make sure that the appropriate class is selected in the class pane.
However, we already use this notation already earlier a few times (method 1.1, method 2.2, method 2.4). Method 1.2 does not use this syntax, however.
We should either introduce the typographic convention earlier or update these three figures to not use the notation.
In sec 2.7, we introduce our typographic convention:
However, we already use this notation already earlier a few times (method 1.1, method 2.2, method 2.4). Method 1.2 does not use this syntax, however.
We should either introduce the typographic convention earlier or update these three figures to not use the notation.
Originally reported here: https://lists.squeakfoundation.org/archives/list/[email protected]/thread/ITFZ56G37BI6W7IY4TC3LC6QOWNZ7M4P/
The text was updated successfully, but these errors were encountered: