File: nil-receiver.mm

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (24 lines) | stat: -rw-r--r-- 556 bytes parent folder | download | duplicates (25) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
// RUN: %clang_analyze_cc1 -analyzer-checker=core,debug.ExprInspection \
// RUN:                    -verify %s

#define nil ((id)0)

void clang_analyzer_eval(int);

struct S {
  int x;
  S();
};

@interface I
@property S s;
@end

void foo() {
  // This produces a zero-initialized structure.
  // FIXME: This very fact does deserve the warning, because zero-initialized
  // structures aren't always valid in C++. It's particularly bad when the
  // object has a vtable.
  S s = ((I *)nil).s;
  clang_analyzer_eval(s.x == 0); // expected-warning{{TRUE}}
}