Sam Steingold <[EMAIL PROTECTED]> writes:
> a superficial code examination shows that these are indeed bugs in
> regex: build_wcs_upper_buffer should be declared to return reg_errcode_t
> and not int.
Thanks for reporting this. I installed the following patch, which I
hope covers all the C++ pro
Paul Eggert wrote:
> Is there some simple
> way that we can work around this in the regex code, without having to
> make wholesale changes? For example, can we surround all the code
> with extern "C" { ... } when compiling with C++?
No, extern "C" only affects the name mangling of symbols and the
> * Paul Eggert <[EMAIL PROTECTED]> [2005-08-23 13:35:05 -0700]:
>
> Sam Steingold <[EMAIL PROTECTED]> writes:
>
>> c++ is stricter, so if the code can be compiled with c++ it is probably
>> safer.
>
> That doesn't match my experience. To make C code work with C++, I
> often have to introduce cast
Sam Steingold <[EMAIL PROTECTED]> writes:
> c++ is stricter, so if the code can be compiled with c++ it is probably
> safer.
That doesn't match my experience. To make C code work with C++, I
often have to introduce casts (e.g., to convert void * to char *, or
to convert one integer type to anoth
> * Ben Pfaff <[EMAIL PROTECTED]> [2005-08-23 11:00:25 -0700]:
> Sam Steingold <[EMAIL PROTECTED]> writes:
>> g++ cannot compile regex, possibly because of K&R style:
> Why is it desirable to compile C code as C++?
c++ is stricter, so if the code can be compiled with c++ it is probably
safer.
also
Sam Steingold <[EMAIL PROTECTED]> writes:
> g++ cannot compile regex, possibly because of K&R style:
Why is it desirable to compile C code as C++?
--
Ben Pfaff
email: [EMAIL PROTECTED]
web: http://benpfaff.org
___
bug-gnulib mailing list
bug-gnulib
> * Paul Eggert <[EMAIL PROTECTED]> [2005-08-20 00:44:38 -0700]:
>
> Sam Steingold <[EMAIL PROTECTED]> writes:
>
>> g++ cannot compile regex, possibly because of K&R style:
>
> I installed the following patch into gnulib in an attempt to fix this,
> and also submitted the corresponding bug reports
