location tracking

[GoogleCodeExporter]

I believe there are a few places where FileLocation is not carried over
appropriately. There should be a debug switch that prints/logs all the
places from which the mk() methods are called without locations.

Original issue reported on code.google.com by radugrig...@gmail.com on 3 Aug 2009 at 3:08

• Blocked on: better location tracking #22

[GoogleCodeExporter]

This issue was updated by revision r606.

You can now log the places from which AST nodes are built
without exlicitely giving a location by saying:
  fb file.bpl -lf=log -lc=ast
A few places in the parser where this was done were fixed.
However, I now believe that it is better to always say
  FileLocation.unknown()
explicitely if the location is not known. This is not high
priority, so I just leave this issue open.

Original comment by radugrig...@gmail.com on 26 Aug 2009 at 4:59

[GoogleCodeExporter]

Depending on how issue 22 is resolved, this one might become a non-issue.

Original comment by radugrig...@gmail.com on 21 Feb 2010 at 6:40