[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnulib and C++
From: |
Ralf Wildenhues |
Subject: |
Re: gnulib and C++ |
Date: |
Thu, 18 Feb 2010 21:05:11 +0100 |
User-agent: |
Mutt/1.5.20 (2009-10-28) |
Hello John,
* John W. Eaton wrote on Thu, Feb 18, 2010 at 08:37:30PM CET:
> However, there is one issue that has caused a bit of trouble as I
> have started using more gnulib modules.
>
> Octave is mostly written in C++ and am having some difficulty with the
> rpl_ redefinitions of symbols that have been used as member function
> names in the Octave sources.
[...]
>
> Is there an easy way that I can determine which symbols *could* be
> redefined by the gnulib modules I'm using when I'm working on a system
> that does not require the redefinitions?
Something like this should be fairly close to producing the exact list:
$ autoconf '--trace=AC_DEFINE:$1:$2' | grep ':rpl_[^:]*$'
> Do other people have these kinds of problems? If so, how are you
> dealing with them?
Unless you're using these functions in the C++ code, I suggest you could
produce a helper header to #undef them again; you could even do that
automatically during bootstrap with above. Then only a portability
layer would need to avoid using these symbols in another namespace.
Hope that helps.
Cheers,
Ralf
- gnulib and C++, John W. Eaton, 2010/02/18
- Re: gnulib and C++,
Ralf Wildenhues <=
Re: gnulib and C++, Bruno Haible, 2010/02/18