File: go_subdir_import_a.i

package info (click to toggle)
swig 4.0.2-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 42,876 kB
  • sloc: cpp: 61,013; ansic: 27,612; java: 14,670; python: 10,632; cs: 8,103; makefile: 6,287; yacc: 6,197; sh: 5,247; ruby: 5,172; perl: 3,541; php: 2,069; ml: 2,066; lisp: 1,894; javascript: 1,300; tcl: 1,091; xml: 115
file content (37 lines) | stat: -rw-r--r-- 1,017 bytes parent folder | download | duplicates (8)
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 whos 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;
}
%}