When you say you want to analyze the source code of an Erlang program, it made me wonder if you were by chance interested in dependency analysis of your program itself. (You might only care to analyze the FSM that you are writing, but I wanted to double check).
If so, Erlang's Xref - The Cross Reference Tool, might be of interest.
I'm a new user, so I can't post another hyperlink, but if you search for "erlang xref graphviz" you will find a post on erlang.org where Ulf W describes connecting Xref to GraphViz.
The next-state in gen_fsm can be a computed value that static source analysis would not be able to find out in the general case.
Of course; with type annotations it would be possible, but then you could just as well write down your state transitions explicitly to generate your .dot file from.
发布评论
评论（3）
此论坛帖子（“我想尝试一些工具，而不是链接 gen_fsm（或其他 erlang FSM）和点（graphviz）文件。”）可能对您有用：
http://www.trapexit.org/forum/viewtopic.php?p=44468
This forum post ("I would like to try some tool than link gen_fsm (or other erlang FSM) and dot (graphviz) file.") might be of use to you:
http://www.trapexit.org/forum/viewtopic.php?p=44468
当你说你想分析 Erlang 程序的源代码时，我想知道你是否偶然对你的程序本身的依赖分析感兴趣。 （您可能只关心分析您正在编写的 FSM，但我想仔细检查）。
如果是这样，Erlang 的 Xref - 交叉引用工具可能会感兴趣。
我是新用户，所以我无法发布另一个超链接，但如果您搜索“erlang xref graphviz”，您会在 erlang.org 上找到一篇文章，其中 Ulf W 描述了将 Xref 连接到 GraphViz。
When you say you want to analyze the source code of an Erlang program, it made me wonder if you were by chance interested in dependency analysis of your program itself. (You might only care to analyze the FSM that you are writing, but I wanted to double check).
If so, Erlang's Xref - The Cross Reference Tool, might be of interest.
I'm a new user, so I can't post another hyperlink, but if you search for "erlang xref graphviz" you will find a post on erlang.org where Ulf W describes connecting Xref to GraphViz.
gen_fsm 中的下一个状态可以是静态源分析在一般情况下无法找到的计算值。
当然;使用类型注释这是可能的，但是您也可以明确地写下您的状态转换以生成您的
.dot文件。The next-state in gen_fsm can be a computed value that static source analysis would not be able to find out in the general case.
Of course; with type annotations it would be possible, but then you could just as well write down your state transitions explicitly to generate your
.dotfile from.