[RFC] Koenig lookup patch 3

[Tom Tromey]

>>>>> "Sami" == Sami Wagiaalla <swagiaal@redhat.com> writes:

Tom> It seems like these additions would introduce a parser ambiguity,
Tom> because UNKNOWN_NAME could be parsed as adl_func or as name_not_typename
Tom> (and hence variable).

Tom> Is bison silent about this?

Sami> Good point. Same goes for everything that is common between name and
Sami> name_no_typename. Anyways I have changed this to:

It still seems like the new productions are ambiguous, because
UNKNOWN_NAME alone is an `exp'.  If bison doesn't give more warnings
after the patch, though, then I wouldn't worry about it.

Sami> 	* c-exp.y: Created token UNKOWN_NAME.
Sami> 	Created grammar rules for UNKOWN_NAME.

Typo: should be `UNKNOWN'.


Other than that this looks good to me.

I was curious to know what happens when the current language is C, not
C++.  Do we still attempt ADL?

Tom