X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <000201c93ac7$38265930$4001a8c0@mycomputer> <490A30C8.5000107@sh.cvut.cz> <001601c93b31$a961b940$4001a8c0@mycomputer> <003e01c93b42$e92a17a0$4001a8c0@mycomputer> <490AE8A0.8090009@sh.cvut.cz> <001a01c93b4d$617de150$4001a8c0@mycomputer> Subject: RE: cygwin g++ strictness Date: Fri, 31 Oct 2008 11:58:57 -0000 Message-ID: <028a01c93b50$0dda69d0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <001a01c93b4d$617de150$4001a8c0@mycomputer> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com John Emmas wrote on 31 October 2008 11:40: > Having said all that, most compilers provide implicit conversions between > related types. Both GCC and MSVC implement the same C and C++ language standards, which define clearly what type conversions are allowed and which are not. Further, the rules are different for C and for C++, and different again when references are involved. Also your previous example was pretty confused: John Emmas wrote on 31 October 2008 10:25: > Here's the compiler's command line:- > gcc.exe That's the C compiler. > -c F:/GTK/HelloWorld/Test.c That's a C source file. Clearly this is nothing to do with the examples you have shown us that rely on C++ references. BTW, Cygwin has gcc v4 packages available; they're named gcc4, gcc4-core, gcc4-g++ and so on. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/