Re: [Help-glpk] python wrapper for glpk

[Andrew Makhorin]

>The main problem I have is that SWIG cannot parse the glpk.h include
>file properly.  SWIG apparently can't parse defines embedded within
>a structure definition.  If you could see to move 6 lines in the
>include file, I could provide a totally automated way to create a
>Python wrapper for glpk.  I understand that clarily may slightly
>suffer, but I think that the benefits outweigh the drawbacks.

If all declarations will be like follows:

struct
{     ...
      int foobar;
#if 0
#define FOO 111
#define BAR 222
#endif
      ...
};

#define FOO 111
#define BAR 222

will SWIG correctly parse them? The reason is that some #defines define
domains for the structure members under which they are written, and to
improve readability I'd like to keep them together.