ParseTree will never be available on 1.9.1.  The Ruby internals don't give
access to the AST.

http://www.infoq.com/news/2009/04/no-parsetree-on-19

Ryan Davis, who is one of the developers behind ParseTree, now makes it
clear in a post on ParseTree's
future<http://blog.zenspider.com/2009/04/parsetree-eol.html>
:

ParseTree is dead on ruby 1.9 and there is no plan to make it work.

Because of changes to internals in 1.9, ParseTree simply can not work. I
asked for hooks/options to allow us to get to the information but they never
arrived.

Specifically if you're using ParseTree to access the AST of a live
method/block/proc, you're SOL. If you're just using ParseTree to do static
analysis, then you can switch to
ruby_parser in about a minute of work and you're good to go.


On Tue, Sep 15, 2009 at 7:16 AM, Xavier Shay <[email protected]> wrote:

>
>
>
> On 15/09/09 9:10 AM, Dan Kubb (dkubb) wrote:
> >
> > Chris,
> >
> >> Can anyone confirm  wether sweatshop is working on 1.9.1?
> >
> > The specs for dm-sweatshop have been passing with Ruby 1.9.1 since the
> > beginning of the year, although I do think there's one feature it
> > can't support due to ParseTree not being available in Ruby 1.9.
> I looked a bit more into it - unique {} is gracefully degredated if
> ParseTree is not available:
>
> "You need to install ParseTree to use an anonymous unique (gem install
> ParseTree). In the mean time, explicitly declare a key: unique(:my_key)
> { ... }"
>
> As such, the unique tests are also not run if ParseTree is not
> available. This excludes tests that should be run - I will change this.
>
> I guess the question is do we want a feature in DM that is only
> supported optionally? I think the anon syntax is neat, but probably it's
> too confusing, esp if we can't get it going on 1.9. Thoughts?
>
> >
> > What sort of problems are you seeing with it?
> >
> > --
> >
> > Dan
> > (dkubb)
> > >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DataMapper" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/datamapper?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to