This binding, 1065, is a legacy binding, provided to support components authored against the beta releases of the first half of 2008. New components should use the 1199 binding, and existing components may run slightly faster, particularly if they are lightweight, if they are upgraded to run against 1199. In addition, not all aspects of this binding are documented, so long-term maintenance will be easier if components are upgraded. See Upgrading to 1199 for information on how to do this.


You should not use this binding for new Components. Use 1199 instead. See Upgrading to 1199 for instructions on upgrading existing Processes from 1065 to 1199, if necessary (you don't have to, but if you need additional support or optimal performance this will help).


  • Since this interface, on paper, makes an additional function call for each event, in comparison with the native C interface, processes may potentially run more slowly than those authored in C. However, any optimizing compiler should eliminate this overhead; failing that, the overhead should be so small as to be immeasurable in any case.
  • Native Events are translated by this binding to legacy 1065 events, and the calling protocol of the event() function is also legacy. See Events1065. This translation, unlikely to be eliminated by an optimizing compiler, may cause this binding to run slower than 1199 or 1266, but the overhead should be negligible in most cases.

Common aspects with 1199

The following aspects are common to this binding and 1199, and are documented in the section for that binding.