Re: [Dev-C++] SOLVED, was: new dev-cpp bombs out on short program

[Per W. <pw...@ia...>]

It's nothing sacred. Dev-C++ uses the MinGW port of the gcc compiler, and
the gcc compiler have the following hard-coded extensions - cut from the
info output on a Linux:

----------
`FILE.c'
     C source code which must be preprocessed.

`FILE.i'
     C source code which should not be preprocessed.

`FILE.ii'
     C++ source code which should not be preprocessed.

`FILE.m'
     Objective-C source code.  Note that you must link with the library
     `libobjc.a' to make an Objective-C program work.

`FILE.mi'
     Objective-C source code which should not be preprocessed.

`FILE.h'
     C header file (not to be compiled or linked).

`FILE.cc'
`FILE.cp'
`FILE.cxx'
`FILE.cpp'
`FILE.c++'
`FILE.C'
     C++ source code which must be preprocessed.  Note that in `.cxx',
     the last two letters must both be literally `x'.  Likewise, `.C'
     refers to a literal capital C.

`FILE.f'
`FILE.for'
`FILE.FOR'
     Fortran source code which should not be preprocessed.

`FILE.F'
`FILE.fpp'
`FILE.FPP'
     Fortran source code which must be preprocessed (with the
     traditional preprocessor).

`FILE.r'
     Fortran source code which must be preprocessed with a RATFOR
     preprocessor (not included with GCC).

     *Note Options Controlling the Kind of Output: (g77)Overall
     Options, for more details of the handling of Fortran input files.

`FILE.ads'
     Ada source code file which contains a library unit declaration (a
     declaration of a package, subprogram, or generic, or a generic
     instantiation), or a library unit renaming declaration (a package,
     generic, or subprogram renaming declaration).  Such files are also
     called "specs".

`FILE.adb'
     Ada source code file containing a library unit body (a subprogram
     or package body).  Such files are also called "bodies".

`FILE.s'
     Assembler code.

`FILE.S'
     Assembler code which must be preprocessed.

`OTHER'
     An object file to be fed straight into linking.  Any file name
     with no recognized suffix is treated this way.

   You can specify the input language explicitly with the `-x' option:

`-x LANGUAGE'
     Specify explicitly the LANGUAGE for the following input files
     (rather than letting the compiler choose a default based on the
     file name suffix).  This option applies to all following input
     files until the next `-x' option.  Possible values for LANGUAGE
     are:
          c  c-header  cpp-output
          c++  c++-cpp-output
          objective-c  objc-cpp-output
          assembler  assembler-with-cpp
          ada
          f77  f77-cpp-input  ratfor
          java
----------

Of course MinGW isn't delivered with all these backends, but this is the
extension-checking supported by gcc. Notice the six different extensions
for a c++ file.

/Per W

On Tue, 8 Jul 2003, R. D. Flowers wrote:

> I repeat. It is solved. It was that .C is a sacred word to the default
> dev-c++ compilers, where I really needed .c .
>
> Smith, Jacob N. wrote:
>
> > "or anyone new to dev-c++ should not need to link in"
> > "Dos non-case-sensitive c-and-asm-only Turbo-C on an XT, the extension was
> > .C, not .c, and dev-c++ took that to mean it was C++"
> >
> > Dev-C++ is a development environment. It sounds like your problem is with
> > GNU/GCC. Please contact the appropriate mailing list (gcc...@gn...) or,
> > alternately, RTFM.
> >
> > -j.
> >
> >
> >
> > .
> >
>
> --
> The Bear At Home
> R. D. Flowers
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Parasoft
> Error proof Web apps, automate testing & more.
> Download & eval WebKing and get a free book.
> www.parasoft.com/bulletproofapps
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>