| |
| | [No title] |
 | | In fact, primitives are essential in a purely applicative system (Joy also relies heavily on primitives (like "dup", "swap", "dip", "map", etc.), rather than fancy constructs; this is in contrast to languages like C and even Haskell, which rely on myriads of fancy constructs). |
 | | A purely applicative approach is simpler in the sense that the only constructs needed are primitives and function-application, while the Joy approach needs at least primitives, concatenation, and quotation... |
 | | But, in a purely applicative system, this setup seems unnatural; functions are primitive in the system (having connections with the system's application construct) and do not need to be emulated using procedures. |
| lists.tunes.org /archives/tunes/2000-February.txt (20665 words) |
|