This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: cygwin g++ strictness


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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]