This page is part of the web mail archives of SRFI 17 from before July 7th, 2015. The new archives for SRFI 17 contain all messages, not just those from before July 7th, 2015.
>>>>> "Jost" == Jost Boekemeier <jostobfe@xxxxxxxxxxxxxxxxxxxxxxxxx> writes: Jost> Mikael Djurfeldt wrote: >> It's quite easy: I did. >> There are several reasons, but the primary one is that we use this >> operator extensively in our object system. We use the accessors to >> get and set values of slots. Ex: >> (set! (n o) 4711) >> means use accessor n to mutate object o so that (n o) returns 4711. Jost> This object system seems to be broken. In any reasonable object Jost> system it is *not* possible to set! the value of one of the object Jost> slots directly. That is nonsense. Multimethod object systems generally work this way, examples being Dylan and CLOS. Jost> You can send a message to an object asking it to change its internal Jost> state. These object systems have no concept of "send[ing] a message to an object," and they can hardly be called unreasonable. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla