<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>20bits - Latest Comments in Erlang: An Introduction to Records | 20bits</title><link>http://20bits.disqus.com/</link><description></description><language>en</language><lastBuildDate>Thu, 19 Jun 2008 11:42:36 -0000</lastBuildDate><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793617</link><description>Good article. Thank you for the concise and clear description of Erlang's records mechanism. It answered a few questions I had about guards,</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alain O'Dea</dc:creator><pubDate>Thu, 19 Jun 2008 11:42:36 -0000</pubDate></item><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793616</link><description>Records were never intended to be anything else other than providing named fields for tuples. In this respect they *are* like C structs and should not be confused with associative arrays, use dict, orddict or gb_trees for that. Or ETS.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Virding</dc:creator><pubDate>Sun, 15 Jun 2008 16:19:55 -0000</pubDate></item><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793612</link><description>Gleb,&lt;br&gt;&lt;br&gt;Good catch.  And thanks for pointing to proplists, I didn't know about them.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jesse</dc:creator><pubDate>Sun, 15 Jun 2008 15:31:17 -0000</pubDate></item><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793613</link><description>website,&lt;br&gt;&lt;br&gt;I'm not sure if you're a real person or a spam bot, but by "a la PHP, Ruby, or Python" I meant as a first-order construct.  I'll reword it so it's less ambiguous.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jesse</dc:creator><pubDate>Sun, 15 Jun 2008 15:23:03 -0000</pubDate></item><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793611</link><description>&amp;gt; so creating associative arrays a la PHP, Ruby, or Python is an impossibility. ... some more bloggery ... &amp;gt; If you want to to add and remove fields on the fly, or if you don't know what fields you'll have until runtime, you should use [dicts](http://www.erlang.org/doc/man/dict.html) rather than records. Huh?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">website design</dc:creator><pubDate>Sun, 15 Jun 2008 13:44:32 -0000</pubDate></item><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793615</link><description>Sorry for double posting.&lt;br&gt;&lt;br&gt;&amp;gt; Perhaps a subset of the first, records are also used to keep track of configurable options. &lt;br&gt;&lt;br&gt;Yes, records may be used for this. But sometimes proplists are better choice, take a look at &lt;a href="http://www.erlang.org/doc/man/proplists.html:" rel="nofollow"&gt;http://www.erlang.org/doc/man/proplists.html:&lt;/a&gt;&lt;br&gt;&lt;br&gt;&amp;gt; Property lists are useful for representing inherited properties, such as &lt;br&gt;&amp;gt; options passed to a function where a user may specify options overriding &lt;br&gt;&amp;gt; the default settings, object properties, annotations, etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gleb Peregud</dc:creator><pubDate>Sun, 15 Jun 2008 09:46:12 -0000</pubDate></item><item><title>Re: Erlang: An Introduction to Records | 20bits</title><link>http://20bits.com/articles/erlang-an-introduction-to-records/#comment-3793614</link><description>In the "Updating Records" there is one issue.&lt;br&gt;&lt;br&gt;Opts = #server_opts{port=80, ip="192.168.0.1"},&lt;br&gt;NewOpts = Opts#{port=7000}.&lt;br&gt;&lt;br&gt;should look like this:&lt;br&gt;&lt;br&gt;Opts = #server_opts{port=80, ip="192.168.0.1"},&lt;br&gt;NewOpts = Opts#server_opts{port=7000}.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gleb Peregud</dc:creator><pubDate>Sun, 15 Jun 2008 09:41:14 -0000</pubDate></item></channel></rss>