4 ms·
> So how can you say some other aspect is more important :-) My opinions only :-) > (Please provide some explanation of what you think is important about " me
by xkriva11 4y ago
> So how can you say some other aspect is more important :-)
My opinions only :-)
> (Please provide some explanation of what you think is important about " method is the basic unit".)
I think it has many interesting consequences. The methods have only a few explicit dependencies required for compilation; they are not dependent on each other, they may be loaded and presented in any order, and the compilation is very fast. As I said, it may be comparable to having every small method in a single file. With such a setup, the code editor itself starts to lose its importance - everything on the level of notepad basically does its job. You need to focus more on the processing of the code as code objects graph. Not as a text file to edit, which may be an important shift in thinking.
Incremental compilation is not related to that directly. And yes, you still need a way how to define classes which Smalltalk file-out format does do as simple do-its, which is not a fortunate solution for statical analysis of the given file.
- igouy 4y ago> … 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" ;-)