Front page | perl.perl5.porters |
Postings from May 2012
On Mon, May 7, 2012 at 1:48 AM, Craig A. Berry <craigberry@mac.com> wrote: > Those dozens or hundreds of you who actually use C++ at the day job and/or know something about C++ parsing rules may want to chime in about whether clang++ has gone slightly bonkers or is just living out its identity as its own eccentric, hypersensitive C++ self. I suspect it's clang++ being bonkers. A nested name specifier is sort of C++'s equivalent of a namespace. Such namespaces are introduced not only by the namespace keyword, but also by types. In this case, it's struct gv that's confusing clang++. I haven't looked up the exact rules, but I really don't think it should be confused, it should just backtrack and interpret gv as an unqualified name. My hunch would be that it's some kind of faulty heuristic acting up (triggered by a colon after a valid typename). LeonThread Previous | Thread Next