Mail Archives: djgpp/2004/04/23/08:45:47
I think it would be somewhat better to appease c++ when you are porting, and
find yourself in an enviroemnt with only c++... The one that comes to mind
in these 'modern' times is C++.net Although what gets me since its a
'syntax' thing, and the compiler can even tells you what to change to make
it happy, why isnt there a switch to have it do the strong types for
you.....
"Hans-Bernhard Broeker" <broeker AT physik DOT rwth-aachen DOT de> wrote in message
news:c6ankb$8m3gj$2 AT ID-231750 DOT news DOT uni-berlin DOT de...
> Alex Vinokur <alexvn AT big DOT foot DOT com> wrote:
> > I prefer to compile C-program with C++ compiler.
>
> I'm pretty sure you won't like to hear this, but: that preference is
> silly to the point of braindead, and has been for a *long* time,
> arguably ever since the first people came up with that idea.
>
> There may have been a point to this strategy back in the days when C++
> compilers actually were better at picking up problems in C code than
> the C compilers of that time. But that time is *over*, and has been
> for about as long as DJGPP exists. GCC is way better at finding
> problematic C code than G++ can ever be.
>
> What is it that you believe you're going to gain from this, compared
> to using the right tool for the task?
>
> *) Use the C++ compiler, for whatever advantages you believe it has, but
> be consequent and write C++ code, then.
>
> *) Write C code and use the C compiler for compiling it.
>
> > $ gpp foo.c
> > error: invalid conversion from `void*' to `unsigned int*'
>
> That error is a false negative created by incorrect use of the tools.
>
> --
> Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
> Even if all the snow were burnt, ashes would remain.
- Raw text -