erlang xml 解析_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 = 'Hello!',

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?

Post Footer automatically generated by wp-posturl plugin for wordpress.

No related posts.