[erlang-questions] New NIF behavior in R15???

[Tim Watson]

My mistake - I haven't used NIFs yet, as most of the native code I've had to
integrate has required threading and I was under the impression that
linked-in drivers are the way to go if you want to avoid blocking the
emulator whilst potentially long running tasks execute.

On 15 October 2011 11:44, Rapsey <rapsey@REDACTED> wrote:

> NIFs already have threading support.
>
>
> Sergej
>
>
> On Sat, Oct 15, 2011 at 11:28 AM, Tim Watson <watson.timothy@REDACTED>wrote:
>
>> I was under the impression that a concept like "Native Processes" was
>> going to be introduced as well, to make the writing of linked-in driver code
>> a lot easier. Is that still on the roadmap as well, and if so why are NIFs
>> getting threading support?
>>
>> On 15 October 2011 02:29, Matthew Evans <mattevans123@REDACTED> wrote:
>>
>>> Hi
>>>
>>> Within the next month or two we will be starting a project interfacing
>>> Erlang to a C driver. This requires the use of a thread pool to support
>>> asynchronous behaviors. Ordinarily I would implement this with a linked in
>>> port driver. However, Rickard Green at his 2011 SF Erlang conference talk
>>> indicated that new support in the NIF framework might be forthcoming in R15
>>> to support linked in driver style threading behavior in NIFS.
>>>
>>> I would rather hold off implementing a linked in driver if the new NIF
>>> features are around the corner. Can anyone give any hints if this will be
>>> the case?
>>>
>>> Thanks
>>>
>>> Matt
>>>
>>> _______________________________________________
>>> erlang-questions mailing list
>>> erlang-questions@REDACTED
>>> http://erlang.org/mailman/listinfo/erlang-questions
>>>
>>>
>>
>> _______________________________________________
>> erlang-questions mailing list
>> erlang-questions@REDACTED
>> http://erlang.org/mailman/listinfo/erlang-questions
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111015/e817a6fc/attachment.htm>