On 11/15/2015 12:01 AM, David Malcolm wrote:
As with the C frontend, there's an issue with tree nodes that don't have locations: VAR_DECL, INTEGER_CST, etc:int test (int foo) { return foo * 100; ^^^ ^^^ } where we'd like to access the source spelling ranges of the expressions during parsing, so that we can use them when reporting parser errors.
Hmm, I had been thinking to address this in the C++ front end by wrapping uses in another tree: NOP_EXPR for rvalues, VIEW_CONVERT_EXPR for lvalues.
Jason
