On Friday, 11 May 2012 at 11:49:23 UTC, Jacob Carlborg wrote:
On 2012-05-11 12:35, Roman D. Boiko wrote:
On Friday, 11 May 2012 at 09:36:28 UTC, Jacob Carlborg wrote:
Aha, clever. As long as I can get out the information I'm
happy :) How
about adding properties for this in the token struct?
There is a method for that in Lexer interface, for me it looks
like it
belongth there and not to token. Version accepting token and
producing a
pair of start/end Locations will be added.
Found it now, "calculateFor". It not sure if it's the most
intuitive name though. I get the feeling: "calculate what?".
calculateLocation was original name, but I don't like repeating
return type in method names, I decided to change it so that it is
clear that another renaming is needed ;) Any suggestions?
That might be the case. But I don't think it belongs in the
parser.
I will provide example code and a dedicated post later to
illustrate my
point.
I guess I'll have to wait for that then :)
I'll try to do that ahead of roadmap, it is important.
