A higher order message (HOM) in a computer programming language is a form of higher-order programming that allows messages that have other messages as arguments. The concept was introduced at MacHack 2003 by Marcel Weiher and presented in a more complete form in 2005 by Marcel Weiher and Stéphane Ducasse. Loops can be written without naming the collections looped over, higher order messages can be viewed as a form of point-free or tacit programming.
Examples.
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, codice_1 is a higher order message, and codice_2 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, codice_1 returns a message that reifies the codice_1 send, which then interprets the codice_2 message.
Another example is the use of future message sends in the Croquet Project:
 (cube future:1000) addRotationAroundY:10.
In this example, the codice_6 message causes the codice_7 message to be sent to the cube object after 1 second.
Adoption.
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 codice_8. Higher order messaging was implemented in a number of languages that share this feature including Ruby and Smalltalk.
ECMAScript Harmony's Proxies documentation specifically mentions higher order messages as an application for their Catchall Proxies.
Similar concepts in other languages.
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 codice_9. message is still sent and has its normal meaning, but its delivery is modified by the codice_10 message, it will be sent sometime in the future.
References.
 ;templatestyles src="Reflist/styles.css" / ;