Re: fnmatch sometimes defined to posix_fnmatch

2011-01-09 Thread John W. Eaton
On 10-Jan-2011, Bruno Haible wrote: | These are simply the old replacement idioms that are not C++ safe. | We introduced the C++ safe idioms for most header files in March 2010, | but the old idioms are still used in a couple of places: | | m4/eaccess.m4:[AC_DEFINE([eaccess], [access], | m4/f

Re: fnmatch sometimes defined to posix_fnmatch

2011-01-09 Thread Bruno Haible
Hi John, > I received a bug report for Octave that was the result of fnmatch > being defined to posix_fnmatch in config.h. I think this is due to > > AC_DEFINE_UNQUOTED([fnmatch], [${gl_fnmatch_required_lowercase}_fnmatch], > [Define to a replacement function name for fnmatch().]) > >

fnmatch sometimes defined to posix_fnmatch

2011-01-09 Thread John W. Eaton
I received a bug report for Octave that was the result of fnmatch being defined to posix_fnmatch in config.h. I think this is due to AC_DEFINE_UNQUOTED([fnmatch], [${gl_fnmatch_required_lowercase}_fnmatch], [Define to a replacement function name for fnmatch().]) in gnulib's fnmatch.m4