[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: g++ free function conflict
From: |
Paul Pluzhnikov |
Subject: |
Re: g++ free function conflict |
Date: |
05 Aug 2004 08:08:00 -0700 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence) |
bluedoze@yahoo.com (BlueDoze) writes:
> bluedoze@yahoo.com (BlueDoze) wrote in message
> news:<a53ecee3.0408040051.3043d5d2@posting.google.com>...
>
> sorry I didn't mean to top post ;-)
Ok, I was about to put you into my kill-file ... :-)
> Actually my question is regarding the different behaviour between
> cygnus compiler and g++ 3.2.3. and I want to check first if there's a
> way to make the g++ 3.2.3 behave in this case as cygnus g++ compiler.
There is no "different behaviour" and there is no way to make
g++-3.2 accept *invalid* C++ code.
Your code compiles under cygwin probably because it doesn't
"#include <malloc.h>" on that platform.
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.