From: Marcin Raczkowski <mailing.mr@...>
Date: 2008-01-06T04:49:23+09:00
Subject: Re: parse tree redux

> complete lack of documentation?!? I write developer tools. I basically 
> expect my user base to be able to read code and I try to write the 
> clearest, smallest code possible such that often doco isn't necessary. 
> But in this case I'm a bit confused:
> 
>     http://parsetree.rubyforge.org/ParseTree/ !!!
> 
> the doco is actually pretty good (coverage wise--I can't judge the 
> content as I don't read it), ~60% according to dcov and it is beating me 
> up on things like my error classes.
> 
Hmmm. Problem is that sometimes when you look for a solution for certain 
problem it's nice if you have short introduction on how to use it.

If you have to evaluate 3-5 solutions and you have to get to know each 
and every one of them it's really time consuming - short summary is not 
enought

Documentation itself is good - true, but it took me few hours of reading 
your blog, wikipedia and source code to understand what was basic 
concept and how i could use it to make my idea work :)

not to mention that someone without solid c background and idea how ruby 
internals work won't be able to understand jack.
I finally got the grasp when i stared inspecting Ruby2Ruby.

and bugs that I reported for Ruby2C were never even acknowledged :)

Aside from that this stuff is really powerfull, and having it when 
working on FreeRIDE coloring and code completion (which i never 
finished) would be awesome.

My idea of transfering ruby code beetween procesing nodes might come 
true. And i would like to really thank you for that :)

greets