Yes, for the moment this is the only one.
In case I need some more I'll send you an email.
thanks a lot
cheers
Lorenzo
Bruno Haible wrote:
Lorenzo Bettini wrote:
I thus included a possible patch.
strdup.h is all you need? Ok, I commit this:
--
+---
Lorenzo Bettini wrote:
> I thus included a possible patch.
strdup.h is all you need? Ok, I commit this:
2006-12-19 Bruno Haible <[EMAIL PROTECTED]>
* lib/strdup.h [C++]: Wrap definitions in extern "C".
Suggested by Lorenzo Bettini <[EMAIL PROTECTED]>.
*** lib/strdup.h1
Bruno Haible wrote:
Lorenzo Bettini wrote:
I tried it and got no problem, but as far as I understand this is not a
proof, since
#if defined HAVE_DECL_STRDUP && !HAVE_DECL_STRDUP && !defined strdup
/* Duplicate S, returning an identical malloc'd string. */
extern char *strdup (const char *s);
#
Lorenzo Bettini wrote:
> I tried it and got no problem, but as far as I understand this is not a
> proof, since
>
> #if defined HAVE_DECL_STRDUP && !HAVE_DECL_STRDUP && !defined strdup
> /* Duplicate S, returning an identical malloc'd string. */
> extern char *strdup (const char *s);
> #endif
>
Bruno Haible wrote:
> Lorenzo Bettini wrote:
>> I've just started using gnulib, and I have a doubt.
>> I've imported strdup and I'm using it in a C++ program.
>>
>> Now should I import strdup.h in the C++ program simply like this
>>
>> #include "strdup.h"
>>
>> Or should I wrap it as follows?
>>
>>
Lorenzo Bettini wrote:
> I've just started using gnulib, and I have a doubt.
> I've imported strdup and I'm using it in a C++ program.
>
> Now should I import strdup.h in the C++ program simply like this
>
> #include "strdup.h"
>
> Or should I wrap it as follows?
>
> extern "C" {
> #include "st
