Higher order message

In ordinary Smalltalk code, without using HOM, obtaining a collection of the employees that have a salary of 1000 would be achieved with the following code:

 salaried := employees select: [ :each | each hasSalary: 1000 ]

However, using HOM, it can be expressed as follows:

 salaried := employees select hasSalary: 1000.

Here, select is a higher order message, and hasSalary: is understood to be called on the select message itself, rather than on its result. The Smalltalk language was not modified to implement this feature. Instead, select returns a message that reifies the select send, which then interprets the hasSalary: message.

Another example is the use of future message sends in the Croquet Project:[4]

 (cube future:1000) addRotationAroundY:10.

In this example, the future: message causes the addRotationARoundY: message to be sent to the cube object after 1 second.

The reference implementation in Objective-C leverages the trait that in Objective-C, objects that don't understand a message sent to them, still get it delivered in a special hook method, called forward:. Higher order messaging was implemented in a number of languages that share this feature including Ruby and Smalltalk.[5]

ECMAScript Harmony's Proxies documentation specifically mentions higher order messages as an application for their Catchall Proxies.[6]

The programming language J distinguishes between verbs and adverbs. Adverbs modify the functioning of verbs. This is similar to higher order messages (the adverbs) modifying the messages that follow (the verbs). In the Croquet example above, the addRotationAroundY:. message is still sent and has its normal meaning, but its delivery is modified by the future:1000 message, it will be sent sometime in the future.