File: go_subdir_import_a.i

package info (click to toggle)
swig 4.4.0-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 45,980 kB
  • sloc: cpp: 54,284; ansic: 29,022; java: 17,595; python: 12,734; cs: 10,421; ruby: 7,263; yacc: 6,501; makefile: 5,860; javascript: 5,538; sh: 5,422; perl: 4,246; php: 3,733; ml: 2,198; tcl: 2,015; lisp: 1,448; xml: 115
file content (37 lines) | stat: -rw-r--r-- 1,018 bytes parent folder | download | duplicates (3)
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
/* File : go_subdir_import_a.i */

/*
 * This files helps check the case where the SWIG-generated .go file needs to
 * import another, SWIG-generated, module that is in a relative subdirectory.
 * This case might happen for two different reasons:
 * 1) Importing a module for which the .i file is in a subdirectory relatively
 *    to this file (this is tested here with go_subdir_import_c).
 * 2) Importing a module whose module name is a path (this is tested here with
 *    go_subdir_import_b).
 *
 * This file is the "root" file that imports the two modules which will be
 * generated (by swig) in a relative subdirectory.
 */
%module go_subdir_import_a

%import(module="testdir/go_subdir_import/go_subdir_import_c") "testdir/go_subdir_import/go_subdir_import_c.i"
%import "go_subdir_import_b.i"

%{
class ObjC {
 public:
  virtual int getInt() const;
};

class ObjB {
 public:
  virtual int getInt() const;
};
%}

%inline %{
int AddFive(const ObjB& b, const ObjC& c) {
  return b.getInt() + c.getInt() + 5;
}
%}