aboutsummaryrefslogtreecommitdiffstats
path: root/gcc-4.9/gcc/testsuite/obj-c++.dg/protocol-qualifier-2.mm
diff options
context:
space:
mode:
Diffstat (limited to 'gcc-4.9/gcc/testsuite/obj-c++.dg/protocol-qualifier-2.mm')
-rw-r--r--gcc-4.9/gcc/testsuite/obj-c++.dg/protocol-qualifier-2.mm31
1 files changed, 31 insertions, 0 deletions
diff --git a/gcc-4.9/gcc/testsuite/obj-c++.dg/protocol-qualifier-2.mm b/gcc-4.9/gcc/testsuite/obj-c++.dg/protocol-qualifier-2.mm
new file mode 100644
index 000000000..fd25d8ff6
--- /dev/null
+++ b/gcc-4.9/gcc/testsuite/obj-c++.dg/protocol-qualifier-2.mm
@@ -0,0 +1,31 @@
+/* Contributed by Nicola Pero <nicola.pero@meta-innovation.com>, November 2010. */
+/* { dg-do compile } */
+
+/* Test that protocol qualifiers are maintained correctly when a
+ @class is replaced by its @interface. */
+
+#include <objc/objc.h>
+
+@protocol MyProtocol
+- (void) method;
+@end
+
+@class MyClass;
+
+static MyClass <MyProtocol> *object1;
+static MyClass *object2;
+
+/* Declarating the @interface now will need to update all the existing
+ ObjC types referring to MyClass with the new information. We need
+ to test that protocol information is not lost in the process. */
+@interface MyClass
+@end
+
+void test1 (void)
+{
+ [object1 method]; /* Ok */
+ [object2 method]; /* { dg-warning ".MyClass. may not respond to ..method." } */
+ /* { dg-warning "without a matching method" "" { target *-*-* } 27 } */
+ /* { dg-warning "will be assumed to return" "" { target *-*-* } 27 } */
+ /* { dg-warning "as arguments" "" { target *-*-* } 27 } */
+}