On 10/15/2007 10:11 AM, Wincent Colaiuta wrote: > El 15/10/2007, a las 14:21, "Pat Maddox" <[EMAIL PROTECTED]> escribió: >> Jay mentioned antlr. This parser is so simple though that I doubt we >> would need/want that. There's not really any parsing at all in fact. >> You just look at each line, figure out what token it is, and pass the >> following string to a constructor. It should be like 60 lines of Ruby >> code, and we don't have any external dependencies. > > I've done a couple of month's work with ANTLR (3.0) this year and > based on my experiences I'd say it's not the right tool for this kind > of job. You use ANTLR if:
Yeah, I think you're right. I'd used ANTLR about eight years ago and got the impression from casual browsing that 3.0 not only solved all those problems, but was moving toward a ruby-hosted toolchain. Guess not. Plus, I've never written a "real" parser, so I always try to find ways to avoid doing so :) Jay _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
