X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <490A33E4.1030904@cygwin.com> Date: Thu, 30 Oct 2008 18:23:32 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080723 Fedora/2.0.0.16-1.fc8 Lightning/0.9 Thunderbird/2.0.0.16 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cygwin g++ strictness References: <000201c93ac7$38265930$4001a8c0 AT mycomputer> In-Reply-To: <000201c93ac7$38265930$4001a8c0@mycomputer> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list 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/