This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: [ECOS] why cygwin does not support "iostream.h"?
- From: "Gareth Pearce" <tilps at hotmail dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 18 Aug 2002 00:00:11 +0000
- Subject: Re: [ECOS] why cygwin does not support "iostream.h"?
- Bcc:
> >
> > I believe this is in the gcc FAQ. However, it's been asked often
enough
> > on this list, so here's an answer for the archives:
> >
> > gcc uses the file extension to determine the language. Any extension
it
> > doesn't recognize is assumed to be a C file. The default extension
for a
> > C++ file is ".C". gcc does not recognize ".cxx", which is used by
> > Microsoft compilers, I think. It is, of course, possible to tell gcc
to
> > treat a ".cxx" file as a C++ file. In case you don't want to mess
with
> > the gcc configuration, use either the "-x c++" option of gcc, or
simply
> > call g++.
> > Igor
>
> Hmm, I suppose I better correct myself before someone else does...
> The default extensions (suffixes) for C++ are ".C", ".cc", ".cpp", and
> ".cxx". Any suffix that is not recognized (e.g., ".o" and ".a") is
passed
> directly to the linker.
What's wrong with me today? :-(
Please strike the ".cpp" suffix. The above should read:
The default suffixes for C++ are ".C", ".cc", and ".cxx".
your 'mistake' was understandable, since ".C", ".cc", ".cxx", ".cp", ".cpp"
and".c++". are all considered c++ in gcc 3.0 and up. (although the person in
this question is obviously using <3.0 since they got it to compile :P)
Gareth
_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/