[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnulib and C++

From: John W. Eaton
Subject: Re: gnulib and C++
Date: Thu, 18 Feb 2010 15:22:39 -0500

On 18-Feb-2010, Ralf Wildenhues wrote:

| 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_[^:]*$'

Running this with the Octave configure.ac file produces only


but I know that this is far from a complete list, as shown by grep
rpl_ on all the files in the libgnu directory of the Octave sources
(where the gnulib module files are copied in the Octave source/build

| 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.

I'd be willing to do something like that if I could somehow generate a
complete list of symbols that could be redefined.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]