2 ms·

I 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 'm

I 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 ago
As 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 ago
  Thanks, I haven't heard about multicast delegates before, and I need to learn more about FRP.