On Thu, Mar 21, 2013 at 10:33 AM, Anthony Ramine <> wrote:
> Maybe, but still if we want diagnostics we need to properly track
> macro expansions.
>
See, it actually helps checking the code :-) Why didn't you mention that
there is a new token attribute, "file"? Suddenly all makes more sense :-)
But there is something missing (or maybe it is in the pipeline) -- the
really useful part would be if the tokens produced by expanding a macro
would point to the file defining it, right?
On the other hand, I would sometimes want to have the tokens for the
non-preprocessed source (for use by the editor) and it would be extra nice
if these could be produced by a single scanning. Maybe we could have
special tokens for that, that are treated by other tools as whitespace? In
this case, the 'end' position is crucial to have because the special macro
tokens will overlap with their expansion.
Maybe this is a discussion better taken in a separate thread, on
erlang-questions?
regards,
/Vlad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-patches/attachments/20130321/e07ccee7/attachment.html>