header file C++ compatibility

[jhoblitt]

Is this sufficient for general C++ compatability or are there other major concerns?

\subsection{C++ Compatibility}

All PSLib public header files should comptable with \code{C++}. This
primarily involves using \code{C} pre-processor directives to enable
\code{C++}'s \code{extern "C"} linkage specification when a header file is being
processed as part of a \code{C++} compilation.

An example of wrapping a header file with an \code{extern "C"} block:

\begin{verbatim}
#ifndef FOO_H
#define FOO_H 1

#ifdef cplusplus
extern "C" {
#endif

...

#ifdef cplusplus
}
#endif

#endif FOO_H
\end{verbatim}

[jhoblitt]

It appears that there are at least three potentional incompatabilties that may
apply to us. C++ users will have to to do some extra work to use pslib's
callbacks as function pointers use a different linkage in c++, there might be
problems with the Complex type(?), and trailing commas in enums might bite us.

enum Color { RED = 0, GREEN, BLUE, }; c++ 98 will barf

​http://david.tribble.com/text/cdiffs.htm#C99-vs-CPP98

[jhoblitt]

It looks like C++ doesn't understand pragmas either. We'll have to do protect
RHL's use of the poison pragma.

[jhoblitt]

C++ doesn't understand restrict either but a quick grep suggests it's been
completely removed from pslib's header files.

[eugene]

this suggestion seems fine to me: i've added it to the SDRS