Forum: Ruby Fwd: First release of Rubyfront

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
912c61d9da47754de7039f4271334a9f?d=identicon&s=25 unknown (Guest)
on 2006-02-17 18:27
(Received via mailing list)
For those interested in things Ruby and grammatical, grammarian Xue
Yong Zhi presents:

----- Forwarded message from yawl.20481481@bloglines.com -----
    Date: 17 Feb 2006 05:22:01 -0000
    From: yawl.20481481@bloglines.com
Reply-To: yawl.20481481@bloglines.com
 Subject: [grammarians] First release of Rubyfront
      To: rubygrammar-grammarians@rubyforge.org

I am glad to announce the first release of rubyfront (a ruby parser
powered by antlr).

Even though this is the first release, rubyfront can parse entire
ruby standard library (over 1500 .rb files).

To download or check out more details about rubyfront, please go to
http://seclib.blogspot.com/2006/02/first-release-o...


Rubyfront uses BSD license. I am going to write more about it on my
blog later.

Xue Yong Zhi
http://seclib.blogspot.com

_______________________________________________
Rubygrammar-grammarians mailing list
Rubygrammar-grammarians@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygrammar-...

----- End forwarded message -----
Eb9493c94d8db9887e5f15284d2c767f?d=identicon&s=25 unknown (Guest)
on 2006-02-18 07:28
(Received via mailing list)
In article <1140197197.43f6074d686cd@www.rydia.net>,  <mental@rydia.net>
wrote:
>I am glad to announce the first release of rubyfront (a ruby parser
>blog later.
>
>Xue Yong Zhi
>http://seclib.blogspot.com
>
>_______________________________________________
>Rubygrammar-grammarians mailing list
>Rubygrammar-grammarians@rubyforge.org
>http://rubyforge.org/mailman/listinfo/rubygrammar-...
>

This seems applicable to JRuby (since it's in ANTLR which is in Java).
How
else might it be used?

Phil
430ea1cba106cc65b7687d66e9df4f06?d=identicon&s=25 David Vallner (Guest)
on 2006-02-18 15:48
(Received via mailing list)
DÅ?a Sobota 18 Február 2006 07:28 Phil Tomson napísal:
> This seems applicable to JRuby (since it's in ANTLR which is in Java).
>

Not necessarily, it should be useful for all sorts of toolchains - it's
just
not possible to invoke it from a Ruby app. It might also be interesting
to
port this to pure Ruby once the ANTLR Ruby backend matures. (Correct me
if
already did since I last checked.) Having a proper Ruby parser in Ruby
might
make writing tools like RDoc much easier.

David Vallner
912c61d9da47754de7039f4271334a9f?d=identicon&s=25 MenTaLguY (Guest)
on 2006-02-18 20:18
(Received via mailing list)
On Sat, 2006-02-18 at 23:46 +0900, David Vallner wrote:

> Not necessarily, it should be useful for all sorts of toolchains -
> it's just not possible to invoke it from a Ruby app. It might also be
> interesting to port this to pure Ruby once the ANTLR Ruby backend
> matures. (Correct me if already did since I last checked.)

I think it's pretty mature now actually, though I haven't played with
it.  The Ruby backend is part of ANTLR v3, though.  yawl's grammar is
for v2.

Martin (the author of the v3 Ruby backend) has a partial v3 Ruby grammar
in TRGP SVN now; I don't know whether we'll ultimately polish that up,
or port yawl's grammar to v3.  At the moment, Ter's leaning towards the
latter, as it's more complete.  But we'll see how it goes.

> Having a proper Ruby parser in Ruby might make writing tools like RDoc
> much easier.

That's the plan.  Not to mention Ruby implementations like JRuby.

I've actually got some evil ideas for a Ruby-in-Javascript
implementation (Ruby in the browser, yay!), but I'm not touching that
one until we have a decent parser waiting in the wings.

-mental
Eb9493c94d8db9887e5f15284d2c767f?d=identicon&s=25 unknown (Guest)
on 2006-02-18 20:39
(Received via mailing list)
In article <200602181546.30323.david@vallner.net>,
David Vallner  <david@vallner.net> wrote:
>already did since I last checked.) Having a proper Ruby parser in Ruby migh=
>t=20
>make writing tools like RDoc much easier.
>

Quite true.  It's been our 'holy grail' for several years now.  I was
not aware
taht ANTLR could generate a pure Ruby parser.

....of course there is Ripper (not sure what the current status is) and
other
similar projects like ParseTree, nodeTree, etc.

Phil
912c61d9da47754de7039f4271334a9f?d=identicon&s=25 MenTaLguY (Guest)
on 2006-02-18 21:49
(Received via mailing list)
On Sun, 2006-02-19 at 04:38 +0900, Phil Tomson wrote:
> Quite true.  It's been our 'holy grail' for several years now.  I was not aware
> taht ANTLR could generate a pure Ruby parser.

The Ruby backend will be new with ANTLR v3.

> ....of course there is Ripper (not sure what the current status is) and other
> similar projects like ParseTree, nodeTree, etc.

Ripper, ParseTree, etc more or less piggyback on the existing parser in
the current Ruby interpreter.

-mental
430ea1cba106cc65b7687d66e9df4f06?d=identicon&s=25 David Vallner (Guest)
on 2006-02-19 13:09
(Received via mailing list)
DÅ?a Sobota 18 Február 2006 20:38 Phil Tomson napísal:
> Quite true.  It's been our 'holy grail' for several years now.  I was not
> aware taht ANTLR could generate a pure Ruby parser.
>
> ....of course there is Ripper (not sure what the current status is) and
> other similar projects like ParseTree, nodeTree, etc.
>

Not to diss all those projects, but ANTLR has that "major" ting to it.
Even if
we had other flawless pure ruby parsers, having an ANTLR grammar around
for
all manners of "Ruby in not-Ruby" weirdness seems to definately to have
perks
by itself.

I wonder if mental is petting a white persia cat plotting his evil
plan...

David Vallner
This topic is locked and can not be replied to.