系统技术非业余研究

Jan 29, 2010
We are very happy to announce the website of Tidier, an automatic
refactoring tool for Erlang programs.

Tidier cleans up Erlang source code and suggests to its user a sequence
of transformations that improve the quality and performance of code.

More information about tidier can be found at its website (*):

http://tidier.softlab.ntua.gr/

We welcome feedback and suggestions!

Kostis Sagonas and Thanassis Avgerinos

俺很期待的东西.试验了下,可以上传erl文件或者整个项目的包上去, tidier果然很争气的找出有问题或者需要改进的地方
,效果相当的好. Erlang R13B04的代码都是经过tidier的. 唯一不好一点就是不开源,使用上有点受限,但是我们还是很感激的.

一起来吧从这里开始: http://tidier.softlab.ntua.gr:20000/tidier/getstarted

在调试版本下 这个工具可以直观的看出你的Erlang程序所用到的锁,对于诊断问题和提高性能非常有帮助.

OTP-8424 Add lock profiling tool.

The Lock profiling tool, lcnt, can make use of the internal lock
statistics when the runtime system is built with this feature
enabled.

This provides a mechanism to examine potential lock bottlenecks
within the runtime itself.

– Add erts_debug:lock_counters({copy_save, bool()}). This option
enables or disables statistics saving for destroyed processes and
ets-tables. Enabling this might consume a lot of memory.

– Add id-numbering for lock classes which is otherwise undefined.

R13B04后erlang的源码编译为了考虑移植性,就改变了编译方式,以下是官方wiki上的安装文档:

1. Cloning

Here are the basic steps to build Erlang/OTP in the Git repository.
Start by cloning:

git clone git://github.com/erlang/otp.git

2. Building

Next, set ERL_TOP the environment variable:

cd otp
export ERL_TOP=`pwd`

The repository does not contain a generated configure file, so it must be generated like this:

./otp_build autoconf

before configure can be run. When the configure files has been generated, you can build in the usual way as described in the README file. Shortly:

./configure
make

3. To run the system you have built without installing it first:

$ERL_TOP/bin/erl 

如题， 方便大家阅读，这个电子书记录了俺的研究过程，希望对大家有帮助。
erlang深度分析文章下载

公司培训用的 凑合看吧 主要讲erlang系统的特点,分布集群以及mnesia的使用, 从比较高的角度来看erlang, 让你有了大体观.

Erlang高级原理和应用

原文地址：http://hyperstruct.net/2007/6/26/literal-xml-in-erlang-with-parse-transform-2

One of the things I dislike about Erlang is that it severely impairs bragging opportunities. Yesterday I wrote a module that allows writing literal XML in the source and have it parsed into Erlang structures at compile time—sort of like E4X minus the manipulation goodies at runtime (at least for now).

You write:

Doc = '<greeting>Hello!</greeting>',
io:format("~p~n", [Doc]).

And it prints…

{xmlElement,greeting,
            greeting,
            [],
            {xmlNamespace,[],[]},
            [],
            1,
            [],
            [{xmlText,[{greeting,1}],1,[],"Hello!",text}],
            [],
            "/tmp",
            undeclared}

In most languages I’m familiar with, this would have granted the author instant Yacc-demigod status. With Erlang… it was less than 40 LOC. Hardly something you’d wear at a party.

Anyway, this code owes everything to Philip’s writings. It also uses parse_transform/2, and “programmers are strongly advised not to engage in parse transformations and no support is offered for problems encountered”. So unless you, like me, are still at the kid-in-a-candy-shop stage of Erlang experience, think twice before using this in production, ok?

The code is here http://repo.hyperstruct.net/inline_xml/

准备把站点改成独立域名了，会慢慢的从javaeye上过渡过来，各位记得更新书签哦。

旧的网站还可以访问: mryufeng.javaeye.com