<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 04/24/2013 06:44 PM, Daniel Goertzen
wrote:<br>
</div>
<blockquote
cite="mid:CAJCf5Ry8o6965Zzoo_N6o5FX29MwU5tL14jjiMdMXcqKkREChQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">It has been a few months since I've begged for
native processes, so it is time to do it again. ;)
<div><br>
</div>
<div>Has there been any progress on NIF native processes? R17?
R18?</div>
</div>
</blockquote>
Native processes *are* in the roadmap, but not likely to be included
in R17. My educated guess would be R18 or later :(<br>
<blockquote
cite="mid:CAJCf5Ry8o6965Zzoo_N6o5FX29MwU5tL14jjiMdMXcqKkREChQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>
It is the simple event() and io_event() callback mechanisms
that really appeal to me, not so much the dirty schedulers.
Is it constructive to separate the two and do
event()/io_event() first and dirty schedulers later?</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Dan.<br>
</div>
</div>
</blockquote>
Best regards,<br>
/Patrik, OTP<br>
<blockquote
cite="mid:CAJCf5Ry8o6965Zzoo_N6o5FX29MwU5tL14jjiMdMXcqKkREChQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
</div>
<div style=""><br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>