{"id":38412,"date":"2023-02-09T16:56:00","date_gmt":"2023-02-09T21:56:00","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=38412"},"modified":"2023-02-09T16:59:06","modified_gmt":"2023-02-09T21:59:06","slug":"clascal-in-the-lisa-source-code","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2023\/02\/09\/clascal-in-the-lisa-source-code\/","title":{"rendered":"Clascal in the Lisa Source Code"},"content":{"rendered":"

Chris Hanson<\/a>:<\/p>\n

\n

While Lisa appears to have an underlying procedural API similar to that of the Macintosh Toolbox, the Office System applications were primarily written in the Clascal<\/em> language—an object-oriented dialect of Pascal designed by Apple with Niklaus Wirth—using the Lisa Application ToolKit<\/em> so they could share as much code as possible between all of them. This framework is the forerunner of most modern frameworks, including MacApp and the NeXT frameworks, which in turn were huge influences on the Java and .NET frameworks.<\/p>\n

[…]<\/p>\n

You define a class and its methods as an interface, and then its implementation doesn’t require repetition. This may sound<\/em> convenient but in the end it means you don’t see the argument lists and return types at definition sites, so everyone wound up just copying & pasting them into comments next to the definition<\/em>!<\/p>\n

[…]<\/p>\n

Just like Macintosh, Lisa has a Memory Manager whose heap is largely organized in terms of relocatable<\/em> blocks referenced by handles<\/em> rather than fixed<\/em> blocks referenced by pointers<\/em>. Thus normally in Pascal one would write SELF^^.h := h;<\/code> to dereference the SELF<\/code> handle and pointer when accessing the object. However, since Clascal knows SELF<\/code> and myPoint<\/code> and so on are objects, it just assumes the dereference—making it hard to get wrong. What I find interesting is that, unlike the Memory Manager on Macintosh, I’ve not seen any references to locking handles so they don’t move during operations. However, since there isn’t any saving and passing around of partially<\/em> dereferenced handles most of the time, I suspect it isn’t actually necessary!<\/p>\n<\/blockquote>\n\n

Chris Hanson<\/a> (Mastodon<\/a>):<\/p>\n

\n

Here’s another interesting thing I’ve learned about Clascal and Object Pascal: It went through exactly the same<\/em> evolution from combining object allocation & initialization to separating them that Objective-C did<\/em> a decade later!<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n