hey, what's the goal ? making a documentation tool? a compiler? a transpiler?
when you say "good usage documentation compared to most existing ones"
what other tool are you talking about? asdoc?
Are you aware that a Java ActionScript 3.0 AST parser already exists?
and it was made by Macromedia/Adobe? and has been open sourced for long time?
asc (ActionScript Compiler)
also check the compiler module
where you can find
In general dev just use the command-line tools (MXMLC, COMPC, ASC, ASDOC)
but if you had very specific needs and wanted to make a custom AS3/MXML compiler
you could use the flex2.oem and start to build your own compiler for example.
If you're not happy with the current documentation tools, flex2.oem could also be used to implement your own asdoc-like tool, or you could start from the asdoc tool itself and patch it for what you need.
I can understand that parser/lexer/tokenizer/etc. are interesting subjects
and rolling your own is an educating/interesting experience, but really why do it (beside the experience of rolling your own)?
Character class is easily clonable/duplicable in any other language, is that the only reason you're using Java ?