error C2059 with extern "C"

I don't think I've encountered this problem before and it confuses me.
I just tried to add SQLite to the project, and I get error.
(Btw, the SQLite source is horrible. Littered with ~450 warnings compiled as C. HORRIBLE!)
In the header, we have this:

Code:

---

#ifdef __cplusplus
extern "C"
{
#endif

---

To make the C code callable from C++ code. Unfortunately, I get the compile error
error C2059: syntax error : 'string'
Whenever the header is included from C++ code, not C code.
extern "C" is invalid in C, so much I know, but it's included from C++ code. The actual SQLite.c file compiles fine.

Any ideas?

Just tried out "sqlite-amalgamation-3_5_6.zip" and it worked fine for me. Is the error in sqlite3.h? In mine, "string" only ever appears in comments.

gg

Yes, sqlite3.h. Here's a sample of the compiler output:
3>Help.cpp
3>g:\w00t\visual studio 2005\projects\sqlite\sqlite3.h(43) : error C2059: syntax error : 'string'
And the error points to
extern "C"

It works fine in a new project. Does that mean there might be some define that's getting in the way...?

Quote:

---

(Btw, the SQLite source is horrible. Littered with ~450 warnings compiled as C. HORRIBLE!)

---

Are you insane? SQLite has probably the best source code out of any open source project I've seen. It is completely readable and well documented. I would love to compare one of your projects of comparable size to SQLite and see who's is more "horrible".

I don't doubt the quality of the written code, but it is horrible in sense that they didn't even bother to silence the warnings.
Ah, now I see the error. Of course. It's located inside a header that is included as part of a template class, hence the error.

That's because it was made to work with many different compilers on many different platforms. It's not as simple as you think.

I don't know. They didn't even try to cast return types from void to char, for example.
But anyway, as long as it works, I'm fine with that.

Quote:

---

I don't doubt the quality of the written code, but it is horrible in sense that they didn't even bother to silence the warnings.

---

D. Richard Hipp is convinced that those warnings are benign. Attempts to convince him otherwise have failed and will fail unless you have solid proof that they need to be fixed.