DISQUS

Great post! Thanks a lot! I'll help me a lot :)

Sorry for double posting.

> Perhaps a subset of the first, records are also used to keep track of configurable options.

Yes, records may be used for this. But sometimes proplists are better choice, take a look at http://www.erlang.org/doc/man/proplists.html:

> Property lists are useful for representing inherited properties, such as
> options passed to a function where a user may specify options overriding
> the default settings, object properties, annotations, etc.

In the "Updating Records" there is one issue.

Opts = #server_opts{port=80, ip="192.168.0.1"},
NewOpts = Opts#{port=7000}.

should look like this:

Opts = #server_opts{port=80, ip="192.168.0.1"},
NewOpts = Opts#server_opts{port=7000}.