|
|
| Author |
Message |
< Erlang ~ "Erlang Programming" uses erl_interface instead of |
| riskyrisk |
Posted: Wed Jul 15, 2009 11:27 pm |
|
|
|
Joined: 11 Oct 2008
Posts: 8
Location: Netherlands
|
I saw a copy of the new book. I'm just wondering why they choose to use erl_interface instead of ei for their c port example? If I remember correctly they use erl_receive_msg in the book instead of ei_receive_msg which I thought was the new and improved version?
And a related question:
Joe uses his own read_cmd c code in his examples. If I'm understanding correctly, life is made easier on us if we use the ei_connect versions?
Thanks
Risky |
|
|
| Back to top |
|
| riskyrisk |
Posted: Thu Jul 16, 2009 11:37 pm |
|
|
|
Joined: 11 Oct 2008
Posts: 8
Location: Netherlands
|
Been reading a bit more...
As I understand it, there are 3 ways to interface with c.
Joe talks about ports and linked-in drivers and the pros and cons. The new book also talks about a 3rd way which is have a c node.
So to refine my question a bit, what are the pros and cons of using a c node versus a port or versus a linked-in driver. I will be using the c for number crunching.
Also which c module(s?) are the current ones to use for each way(node, port, driver)? I'm still confused on erl_interface vs. ei and ei_connect
Thanks again
Risky |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
|
|
|