On Mon, 19 Sep 2005, Paul Eggert wrote: > "Joel E. Denny" <[EMAIL PROTECTED]> writes: > > > int* p = malloc(n*sizeof(int)); > > > > Are you saying g++-4 and g++-5 don't catch it as they should? > > Mine didn't, no. At this point I'm not all that curious as to why.
Neither am I, actually. It shouldn't happen, and, if it is, I assume it'll be fixed in g++ one day. I still use 3.4.1, so I'm safe for now. > > Just out of curiosity, why is your test suite calling g++ for that test > > case anyway? > > Some people like to use C++ compilers when C compilers are called for. > Personally I don't think it's worth catering to such usage, but I > guess others disagree. I'm certainly guilty of using g++ when compiling bison-generated code... even from yacc.c and glr.c. That seems necessary given that the C++ skeletons aren't ready. However, when building bison itself, I don't understand why g++ would be used. I guess it's a moot point, but it's curious. Joel
