<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Erlang First Post</title>
	<atom:link href="http://www.zorched.net/2008/05/27/erlang-first-post/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.zorched.net/2008/05/27/erlang-first-post/</link>
	<description>Musings of a software developer in Milwaukee, WI.</description>
	<pubDate>Thu, 20 Nov 2008 18:11:00 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Geoff Lane</title>
		<link>http://www.zorched.net/2008/05/27/erlang-first-post/#comment-11752</link>
		<dc:creator>Geoff Lane</dc:creator>
		<pubDate>Wed, 28 May 2008 15:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.zorched.net/?p=105#comment-11752</guid>
		<description>Grant,
You're getting beyond my knowledge real fast... but I'll give it a shot. :)
Elang has a couple of notions. Ports and Drivers. 

Ports are basically external processes that you interact with very much like other Erlang processes. It has a few special methods that allow you to send bytes to them for example. This can be anything from a manually loaded library to an executable that you run from within Erlang by supplying the command.

FFI (Foreign Function Interface) is handled by what they call Linked In Drivers. My novice understanding is that Erlang provides some C API that you have to use to integrate existing code. That C code then becomes a shared library that can be loaded into the Erlang runtime and executed.

Erlang does not have an imperative style to "bridge" to imperative languages to my knowledge.</description>
		<content:encoded><![CDATA[<p>Grant,<br />
You&#8217;re getting beyond my knowledge real fast&#8230; but I&#8217;ll give it a shot. :)<br />
Elang has a couple of notions. Ports and Drivers. </p>
<p>Ports are basically external processes that you interact with very much like other Erlang processes. It has a few special methods that allow you to send bytes to them for example. This can be anything from a manually loaded library to an executable that you run from within Erlang by supplying the command.</p>
<p>FFI (Foreign Function Interface) is handled by what they call Linked In Drivers. My novice understanding is that Erlang provides some C API that you have to use to integrate existing code. That C code then becomes a shared library that can be loaded into the Erlang runtime and executed.</p>
<p>Erlang does not have an imperative style to &#8220;bridge&#8221; to imperative languages to my knowledge.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Grant Rettke</title>
		<link>http://www.zorched.net/2008/05/27/erlang-first-post/#comment-11749</link>
		<dc:creator>Grant Rettke</dc:creator>
		<pubDate>Wed, 28 May 2008 14:43:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.zorched.net/?p=105#comment-11749</guid>
		<description>Erlang is purely functional, how do you do imperative coding, for example FFI to C?</description>
		<content:encoded><![CDATA[<p>Erlang is purely functional, how do you do imperative coding, for example FFI to C?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
