[Lapackpp-devel] g2c.h vs f2c.h

[NAKATA M. <ch...@ma...>]

Dear all,
I found an interesting difference between FreeBSD's g2c.h
and f2c.h

g2c.h
/* F2C_INTEGER will normally be `int' but would be `long' on 16-bit systems */
/* we assume short, float are OK */
typedef int /* long int */ integer;
typedef unsigned long int /* long */ uinteger;
typedef char *address;
typedef short int shortint;
typedef float real;
typedef double doublereal;
typedef struct { real r, i; } complex;
typedef struct { doublereal r, i; } doublecomplex;
typedef int /* long int */ logical;
typedef short int shortlogical;
typedef char logical1;
typedef char integer1;
typedef long long int /* long long */ longint;          /* system-dependent */
typedef unsigned long long int /* long long */ ulongint;        /* system-dependent */

f2c.h
typedef long int integer;
typedef char *address;
typedef short int shortint;
typedef float f2c_real;
typedef double doublereal;
typedef struct { f2c_real r, i; } f2c_complex;
/** @brief Complex type that is used in LAPACK++ internally. 

this induced type conflicts. how do we do...?

--nakata maho