ParseTree is a C extension (using RubyInline) that extracts the parse
tree for an entire class or a specific method and returns it as a
s-expression (aka sexp) using ruby's arrays, strings, symbols, and
integers.
As an example:
def conditional1(arg1)
if arg1 == 0 then
return 1
end
return 0
end
* Added gauntlet_parsetree.rb. Bug finding/fixing much faster & easier now.
* Fixed alias tests for r2r. Added masgn and heredoc tests.
* Fixed conflicting flags (-u vs -r).
* Unwrap RHS from array IF it is only a splat node.
ParseTree is a C extension (using RubyInline) that extracts the parse
tree for an entire class or a specific method and returns it as a
s-expression (aka sexp) using ruby's arrays, strings, symbols, and
integers.
As an example:
def conditional1(arg1)
if arg1 == 0 then
return 1
end
return 0
end
* Added gauntlet_parsetree.rb. Bug finding/fixing much faster &
easier now.
* Fixed alias tests for r2r. Added masgn and heredoc tests.
* Fixed conflicting flags (-u vs -r).
* Unwrap RHS from array IF it is only a splat node.
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
If you have installed the build tools (gcc and such) then using
RubyInline and ParseTree shouldn't be much problem for you.
Slow, yes, but maybe not lot of problems
When I tried (please don't ask me to reproduce the bug because I have moved on, and it should be easy), RubyInline kept getting stuck trying to rewrite its library at ~/.ruby_inline/blah_RubyInline_blah.so.
The blah is not important because the root problem was something left zombie ruby.exe processes in memory - they apparently locked their previous .so files.
(And will Ruby1.9's ParseTree use RubyInline or Ripper?)
> If you have installed the build tools (gcc and such) then using
> RubyInline and ParseTree shouldn't be much problem for you.
> Slow, yes, but maybe not lot of problems
When I tried (please don't ask me to reproduce the bug because I have moved on,
and it should be easy), RubyInline kept getting stuck trying to rewrite its
library at ~/.ruby_inline/blah_RubyInline_blah.so.
Well, cannot say about cygwin, I don't have it installed nor plan to
do it.
The blah is not important because the root problem was something left zombie
ruby.exe processes in memory - they apparently locked their previous .so files.
Ah, that Windows IO. file descriptors open (zombies) locks the files,
and you cannot remove or anything.
···
On Jan 21, 5:42 pm, Phlip <phlip2...@gmail.com> wrote:
