Re: Calling for advice on a parser's location data

2010-05-02 Thread Heinz N. Gies
On May 3, 2010, at 3:29 , joshua-choi wrote: > Can you think of an instance where the location would not be a line > number and column number, such as {:line 3, :column 25}? I'd also add :file there (while this does not need to be a physical one it can come in handy) -- You received this mess

Re: Calling for advice on a parser's location data

2010-05-02 Thread Timothy Washington
Unless you're dealing with 1) binary data or 2) structured data (ie. XML) where a path is more appropriate, then I think line / column is the way to go. Now, is this a clojure parser? Or a clojure parser generator library that consumes a BNF-like file that defines another lang? As far as I can tel

Re: Calling for advice on a parser's location data

2010-05-02 Thread Richard Lyman
On Sun, May 2, 2010 at 6:29 PM, joshua-choi wrote: > I'm making a parsing library that can keep track of its location in a > stream of tokens, and the tokens can be of any type—character, map, > and so forth. I need advice on this question: > > Can you think of an instance where the location would

Calling for advice on a parser's location data

2010-05-02 Thread joshua-choi
I'm making a parsing library that can keep track of its location in a stream of tokens, and the tokens can be of any type—character, map, and so forth. I need advice on this question: Can you think of an instance where the location would not be a line number and column number, such as {:line 3, :c