File: protocol-qualifier-1.m

package info (click to toggle)
gcc-arm-none-eabi 15%3A14.2.rel1-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 1,099,328 kB
  • sloc: cpp: 3,627,108; ansic: 2,571,498; ada: 834,230; f90: 235,082; makefile: 79,231; asm: 74,984; xml: 51,692; exp: 39,736; sh: 33,298; objc: 15,629; python: 15,069; fortran: 14,429; pascal: 7,003; awk: 5,070; perl: 3,106; ml: 285; lisp: 253; lex: 204; haskell: 135
file content (33 lines) | stat: -rw-r--r-- 820 bytes parent folder | download | duplicates (12) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
 
/* Contributed by Nicola Pero <nicola.pero@meta-innovation.com>, November 2010.  */
/* { dg-do compile } */

/* Test that protocol qualifiers work in the same way with @class and @interface.  */

#include <objc/objc.h>

@protocol MyProtocol
- (void) method;
@end


/* This first snippet gives no warnings, which is correct as 'object'
   implements <MyProtocol> and hence responds to 'method'.  Note how
   the details of the class 'MyClass' are never used.  */
@interface MyClass
@end

void test (MyClass <MyProtocol> *object)
{
  [object method];
}


/* This second snippet should behave identically.  'object' still implements
   the same protocol and responds to 'method'.  The details of MyClass or
   MyClass2 are irrelevant.  */
@class MyClass2;

void test2 (MyClass2 <MyProtocol> *object)
{
  [object method];
}