llvm-project/clang/test/Parser/cxx-using-directive.cpp

41 lines
890 B
C++
Raw Normal View History

// RUN: clang-cc -fsyntax-only -verify %s
class A {};
namespace B {
namespace A {}
using namespace A ;
}
namespace C {}
namespace D {
class C {
using namespace B ; // expected-error{{not allowed}}
};
namespace B {}
using namespace C ;
using namespace B::A ; // expected-error{{expected namespace name}}
//FIXME: would be nice to note, that A is not member of D::B
using namespace ::B::A ;
using namespace ::D::C ; // expected-error{{expected namespace name}}
}
using namespace ! ; // expected-error{{expected namespace name}}
using namespace A ; // expected-error{{expected namespace name}}
Introduce code modification hints into the diagnostics system. When we know how to recover from an error, we can attach a hint to the diagnostic that states how to modify the code, which can be one of: - Insert some new code (a text string) at a particular source location - Remove the code within a given range - Replace the code within a given range with some new code (a text string) Right now, we use these hints to annotate diagnostic information. For example, if one uses the '>>' in a template argument in C++98, as in this code: template<int I> class B { }; B<1000 >> 2> *b1; we'll warn that the behavior will change in C++0x. The fix is to insert parenthese, so we use code insertion annotations to illustrate where the parentheses go: test.cpp:10:10: warning: use of right-shift operator ('>>') in template argument will require parentheses in C++0x B<1000 >> 2> *b1; ^ ( ) Use of these annotations is partially implemented for HTML diagnostics, but it's not (yet) producing valid HTML, which may be related to PR2386, so it has been #if 0'd out. In this future, we could consider hooking this mechanism up to the rewriter to actually try to fix these problems during compilation (or, after a compilation whose only errors have fixes). For now, however, I suggest that we use these code modification hints whenever we can, so that we get better diagnostics now and will have better coverage when we find better ways to use this information. This also fixes PR3410 by placing the complaint about missing tokens just after the previous token (rather than at the location of the next token). llvm-svn: 65570
2009-02-27 05:00:50 +08:00
using namespace ::A // expected-error{{expected namespace name}} \
// expected-error{{expected ';' after namespace name}}
B ;
void test_nslookup() {
int B;
class C;
using namespace B;
using namespace C;
}