3

I've got a file that I want to parse with Treetop. If I wanted to parse the entire thing, I'd use 

rule document
  category_listing*
end

I don't really want to read the entire file into memory at once. I know I can set up the parser to parse one category_listing at a time (using #consume_all_input = false and #root = :category_listing), which is half the problem. However, it looks like #parse expects to be passed a String (and it certainly fails when I try to pass it a File), which makes the idea of reading and parsing category_listing by category_listing sound like a PITA.

Can Treetop only be used to parse Strings? I've been poking around the treetop docs, but haven't found anything definitive.

rampion
  • 87,131
  • 49
  • 199
  • 315
  • 1
    It's kind of crazy, but you could split your `input` string into chunks, parse each chunk until it returns `nil`, then parse the next chunk starting at the `input.index` of the last successful parse. Do this until the whole thing parses. This is all assuming that the chunk to be parsed is larger than what needs to be parsed. But, to answer your question, no, it doesn't look like it can accept files as input. – Josh Voigts Dec 01 '12 at 17:02

1 Answers1

0

As far as I can glance from the source code, you can indeed only pass a String in. So your options are basically to either follow the idea of Josh Voigts in his comment or to implement something of a reverse IOString: something that has a String interface, but 'lazily' fetches the requested contents from a File.

I'm not entirely sure whether that is even possible without resorting to C and even then there may be methods whose semantics are such that they simply cannot be implemented consistently, but perhaps the subset of String methods used by Treetop is such that it is manageable. However, I'd say Josh Voigts answer is most pragmatic.

Confusion
  • 16,256
  • 8
  • 46
  • 71