3 ms·
Inner-platform effect in the land of nouns. Most programming languages already have operations, you don't need to tack them on as objects, objects generally pe
by fleitz 13y ago
Inner-platform effect in the land of nouns.
Most programming languages already have operations, you don't need to tack them on as objects, objects generally perform one of these operations when passed a message.
'events' are generally known as 'messages' and are again built into the language.
So now we're left with MV, we just need some sort of object that can send/receive messages from views and models. I think I'll call this object a controller.
- SupremumLimit 13y agoI think you make a good point, but there seems to be more to the OP's events and operations than you suggest. The 'events' are implied to be broadcast versus 'messages' which are sent to a particular object (i.e. point-to-point) in languages that I know. The OP is also suggesting a hierarchy of 'operations', with sub-operations communicating with the parent operations. I don't think this maps directly onto language features (again, in languages I'm aware of). I'd be interested to hear which languages you had in mind, and some more detail on how you envisage the mapping to language features.
- fleitz 13y agoAs for operations communicating this is generally known as a return value. Parent operations and sub operations is just cleverly disguised procedural programming. It sounds like half procedural programming, half partial application. 'Events' sounds alot like [NSArray makeObjectsPerformSelector] / KVO/KVC / Multicast delegate. Honestly, the more I think about it the more MOVE sounds like functional reactive programming.
- SupremumLimit 13y agoThanks, I haven't heard about multicast delegates before, and I need to learn more about FRP.