Erlang linked in drivers, ErlDrvEntry structure
sergey-miryanov
sergey.miryanov@REDACTED
Thu Feb 25 06:25:02 CET 2010
Do you see this: http://www.erlang.org/doc/man/driver_entry.html?
On Feb 25, 7:13 am, "Evans, Matthew" <mev...@REDACTED> wrote:
> Hi All,
>
> I've been looking at linkedin drivers a little. I 'm trying to find a description of all the handler functions that are contained in the ErlDrvEntry structure. Obviously startup and shutdown make sense, but what about all the others (see the example below)? When are they called (for example ready_input, handle, control, process)? Pointers to documentation would be helpful, the Erlang documentation inhttp://www.erlang.org/doc/man/erl_driver.htmlseems to be missing quite a few of them....
>
> Many thanks
>
> Matt
>
> static ErlDrvEntry basic_driver_entry = {
> NULL, /* init */
> start, /* startup */
> stop, /* shutdown */
> NULL, /* output */
> NULL, /* ready_input */
> NULL, /* ready_output */
> "basic_drv", /* the name of the driver */
> NULL, /* finish */
> NULL, /* handle */
> NULL, /* control */
> NULL, /* timeout */
> process, /* process */
> NULL, /* ready_async */
> NULL, /* flush */
> NULL, /* call */
> NULL, /* event */
> ERL_DRV_EXTENDED_MARKER, /* ERL_DRV_EXTENDED_MARKER */
> ERL_DRV_EXTENDED_MAJOR_VERSION, /* ERL_DRV_EXTENDED_MAJOR_VERSION */
> ERL_DRV_EXTENDED_MAJOR_VERSION, /* ERL_DRV_EXTENDED_MINOR_VERSION */
> ERL_DRV_FLAG_USE_PORT_LOCKING /* ERL_DRV_FLAGs */
>
> };
>
> ________________________________________________________________
> erlang-questions (at) erlang.org mailing list.
> Seehttp://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-questions-unsubscr...@REDACTED
More information about the erlang-questions
mailing list