{"id":20479,"date":"2023-02-01T03:31:43","date_gmt":"2023-02-01T03:31:43","guid":{"rendered":"https:\/\/www.booksofall.com\/tw\/?post_type=product&p=20479"},"modified":"2023-02-01T03:31:43","modified_gmt":"2023-02-01T03:31:43","slug":"coolaid-the-cool-2013-reference-manual","status":"publish","type":"product","link":"https:\/\/www.booksofall.com\/tw\/coolaid-the-cool-2013-reference-manual\/","title":{"rendered":"CoolAid: The Cool 2013 Reference Manual"},"content":{"rendered":"

This manual describes the programming language Cool<\/a>: the Classroom Object-Oriented Language<\/a>. Cool is a small language that can be implemented with reasonable effort in a one semester course. Still, Cool retains many of the features of modern programming languages<\/a> including objects, static typing<\/a>, and automatic memory management<\/a>.<\/p>\n

Cool programs are sets of classes. A class encapsulates the variables and procedures of a data type. Instances of a class are objects. In Cool, classes and types are identified; i.e., every class defines a type. Classes permit programmers to define new types and associated procedures (or methods) specific to those types. Inheritance allows new types to extend the behavior of existing types.<\/p>\n

Cool is an expression language. Most Cool constructs are expressions, and every expression has a value and a type. Cool is type safe: procedures are guaranteed to be applied to data of the correct type. While static typing imposes a strong discipline on programming in Cool, it guarantees that no runtime type errors can arise in the execution of Cool programs.<\/p>\n

This manual is divided into informal and formal components. For a short, informal overview, the first 12 pages (through Section 9) suffices. The formal description begins with Section 10.<\/p>\n

\n","protected":false},"excerpt":{"rendered":"