[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: alloca redeclaration warning on MinGW
From: |
Hrvoje Niksic |
Subject: |
Re: alloca redeclaration warning on MinGW |
Date: |
Sat, 02 Jul 2005 12:21:03 +0200 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, linux) |
Paul Eggert <address@hidden> writes:
> This doesn't look right to me, because if _MSC_VER is defined, it
> includes <malloc.h> without the "# define alloca _alloca" line that
> other people seem to have needed.
I haven't needed that line in Wget. Maybe it was needed in older
versions of Visual C?
> What's the story on alloca versus _alloca in <malloc.h>?
I've seen other external function prefixed with "_" as well, but I
don't know the story behind them.
> Also, what is the difference between _MSC_VER, __BORLANDC__, and
> __MINGW32__? Are these different compilers?
They are different compilers. What they have in common is that they
(these days) run in the Win32 environment, which means that all of
them have <malloc.h>, which appears to be a standard Win32 headers.
Since the declaration already checked for _MSC_VER, it makes at least
as much sense to check for __BORLANDC__ and others.
> (Please bear in mind that I don't use DOS-related platforms so
> you'll have to explain obvious things.)
I don't use them either, but my users do, so I had to learn more about
them than is pleasant.