Erlang to driver communication: why not a non-serialized opti on?

Scott Lystig Fritchie fritchie@REDACTED
Thu Apr 25 02:55:13 CEST 2002

>>>>> "jh" == James Hague <jamesh@REDACTED> writes:

>> The second (and much larger) erosion was the introduction of
>> driver_output_term() and driver_send_term(). [...]
>> The third erosion is something that snuck in with R8 (?),
>> erlang:port_call/3.

jh> Are there examples of either of these?  It seems that the
jh> documentation has gotten very behind in this area.

A find + xargs grep of the OTP R8 Erlang code didn't find any usage of
erlang:port_call/3.  The R8 docs mention it in the "erlang" section of
the Kernel Reference Manual, but it is misalphabetized: it appears
between port_control and erlang:port_info.

The only driver that appears to use driver_output_term() or
driver_send_term() is the inet_drv driver, found in
erts/emulator/drivers/common/inet_drv.c; it uses both.


More information about the erlang-questions mailing list