This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cygwin g++ strictness
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 30 Oct 2008 18:23:32 -0400
- Subject: Re: cygwin g++ strictness
- References: <000201c93ac7$38265930$4001a8c0@mycomputer>
- Reply-to: cygwin at cygwin dot com
John Emmas wrote:
When compiling things under cygwin I'm noticing that the compiler is very
strict about things like typedef'd variables. For example if 'gint' is
typedef'd as int and 'int32' is also typedef'd as int I can't pass an int32
to a function that requires gint. This means I'm having to put dozens of
casts all over the place. Is there any way to avoid this? e.g. a compiler
switch that would make the compiler a bit more lenient?
This is gcc/g++ question, not a Cygwin one. Please find an appropriate
forum to ask this question if you can't find it in the available
documentation.
Thanks,
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/