File: imports_b.i

package info (click to toggle)
renderdoc 1.2%2Bdfsg-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 79,584 kB
  • sloc: cpp: 491,671; ansic: 285,823; python: 12,617; java: 11,345; cs: 7,181; makefile: 6,703; yacc: 5,682; ruby: 4,648; perl: 3,461; php: 2,119; sh: 2,068; lisp: 1,835; tcl: 1,068; ml: 747; xml: 137
file content (47 lines) | stat: -rw-r--r-- 1,017 bytes parent folder | download | duplicates (14)
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
34
35
36
37
38
39
40
41
42
43
44
45
46
47
/* This file is part of a test for SF bug #231619. 
   It shows that the %import directive does not work properly in SWIG
   1.3a5:  Type information is not properly generated if a base class
   comes from an %import-ed file. 

   Extra tests added for enums to test languages that have enum types.
*/

%module imports_b

%{ 
#include "imports_b.h" 
%} 


/* 
   To import, you can use either
   
     %import "imports_a.i"

   or

     %import(module="imports_a") "imports_a.h" 


   In the first case, imports_a.i should declare the module name using
   the %module directive.

   In the second case, the file could be either a .h file, where no
   %module directive will be found, or a swig interface file, where
   the module option will take priority over any %module directive
   inside the imported file.

*/

#if 0
  %import "imports_a.i"
#else
#  if 0
  // Test Warning 401 (Python only)
  %import "imports_a.h" 
#  else
  %import(module="imports_a") "imports_a.h" 
#  endif
#endif

%include "imports_b.h"