mex.h does not include config.h

[John W. Eaton]

On 19-May-2009, Kris Thielemans wrote:

| When using mex.h, I need to #include "config.h" to get my files to compile
| (using Octave 3.0.3). That seems unnecessary (and is definitely not the case
| in matlab). Therefore, I recommend to add a #include "config.h" statement to
| mex.h.

What do you need config.h for when compiling a MEX file with Octave?
What fails if you don't?  I don't seem to need to include any config.h
file when compiling a MEX function with "mkoctfile --mex" and Octave
3.0.5.

| By the way, I'd also recommend to rename config.h to octave_config.h or
| something to avoid name clashes with other configuration settings. That
| would break backwards compatibility of course, so maybe you could still
| supply config.h that simply includes octave_config.h but never use it
| yourself (including in the documentation).

Yes, config.h should probably not be installed with the name config.h.
I hope to fix this after 3.2 is released.

jwe