On 6/3/19 1:30 PM, Jason Merrill wrote:
On 5/31/19 1:39 PM, Nathan Sidwell wrote:
The fallout is some error cascade on symbol lookups that now fail.
Right, that's why we had the previous behavior, to avoid this extra
noise. And then various places check error_operand_p to avoid trying to
do anything with such a declaration.
Perhaps lookup should return error_mark_node rather than a _DECL with
error_mark_node type?
Good idea, but still fails in simlar ways. I think that's because with
the curren tbehaviour, it can parse suchan erronous typedef name as a
declspec seq -- and a var-decl as a var (I now see we set their type to
error_mark_node too). This is looking like a rat hole :(
nathan
--
Nathan Sidwell
