> … not dependent on each other… Unless they are — methods that change how methods are compiled. > … loaded and presented in any order… And which may give di

> … not dependent on each other… Unless they are — methods that change how methods are compiled. > … loaded and presented in any order… And which may give different results depending on order. Isn't that what "First-Class Undefined Classes for Pharo" was about? https://hal.archives-ouvertes.fr/hal-01585305/document https://hal.archives-ouvertes.fr/hal-01585305/document > … how to define classes which Smalltalk file-out format… That problem isn't created by the file-out format. That problem is everything is a message send. "Class definitions are [not] static, declarative syntactic structures." 1988 "An Overview of Modular Smalltalk" https://dl.acm.org/doi/pdf/10.1145/62084.62095 https://dl.acm.org/doi/pdf/10.1145/62084.62095 Seems like there have been plenty of problems caused by "method is the basic unit" ;-)