Re: [Swig-devel] Octave language module

[Xavier D. <xav...@gm...>]

>  - Could you please run the beautify-file target on octave.cxx, check the
>  output and make any necessary minor mods (it is not perfect) and try
>  follow the resulting coding style.
>  - Can you read the Makefile and run make in the Doc/Manual directory and
>  fix up the html.

Sure, I'll do these before I check in next.

>  - What is the state for C support? I see C++ in core areas of the runtime.

The module will wrap both C and C++ code in its present state, or
close to it. Maybe a fix is required to add extern "C" around C
decls/includes, although that seems like the responsibility of the
user. In the examples, the .c examples are actually built using the
C++ compiler.

The wrapper code itself must be C++ because Octave itself is written
in C++. E.g., creating custom types requires deriving from one of
their classes (octave_base_value). A bridge could be added to Octave
or a third library, but I don't really see the point.

I would prefer simply forcing on the -c++ option, or complaining when
it isn't set. Though perhaps I'm misunderstanding the requirement.

Xavier