<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
On 04/12/2016 10:40 AM, Benoit Chesneau wrote:<br>
<blockquote
cite="mid:CAJNb-9oVqgH3JmyG+1QsEzpnVS4Asb_c5b0xNR+zMu9HrMaknQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div dir="ltr">I'm not sure to understand what can I expect from
the return of enif_schedule_nif. The doc says:<br>
<br>
Be aware that enif_schedule_nif, as its name implies, only
schedules the NIF for future execution. The calling NIF does not
block waiting for the scheduled NIF to execute and return, which
means that the calling NIF can't expect to receive the scheduled
NIF return value and use it for further operations.<br>
<br>
So should I handle to return the data asynchronously to the
calling process using enf_send? In that case what is the return
of the function?<br>
<div><span><span
style="color:rgb(0,0,0);font-family:Verdana,Arial,Helvetica,sans-serif;font-size:medium"><br>
</span></span></div>
<br>
</div>
</blockquote>
No. The return value of your scheduled function<br>
will be the return value from your original Erlang nif call.<br>
<br>
<br>
/Sverker, Erlang/OTP<br>
<br>
<br>
<br>
<br>
</body>
</html>