just a few ideas. I do not want to mess with yaws_compile myself,
but maybe someone finds them compelling enough to implement.
* If the HTML part before the first or after the last Erlang part is
white space only, I think it should be discarded. Especially since
it is hard to avoid having the editor add a newline after the final
* In case one wants to use an HTML tool to parse a `.yaws' file, it
would be helpful, if it was possible to put Erlang code between
`<erl><!--' and `--></erl>', to make the HTML tool ignore it or
copy it verbatim.
* You cannot refer to functions defined in a different Erlang part of
the same file. This is solved better in PHP. *eg*
I just came up with the idea of allowing something like
bar(X) -> ....
out(A) -> ...
This one is less trivial than the first two, but probably not
hard. I do not know if it is worth the effort, though.
Carsten Schultz (2:38, 33:47), FB Mathematik, FU Berlin
PGP/GPG key on the pgp.net key servers,=20
fingerprint on my home page.
Get latest updates about Open Source Projects, Conferences and News.