[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Mixed C/C++ in MBS
|
>I'm not at all suggesting for example Fortran in the same project,
mixed
>Fortran and C/C++ are very rare.
It's all a matter of perspective. If you are primarily a Fortran
programmer, then mixed Fortran and C is VERY common. If you are
primarily a C programmer, then it's not.
Leo
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Duane Ellis
Sent: Monday, February 27, 2006 9:35 AM
To: cdt-dev@xxxxxxxxxxx
Subject: RE: [cdt-dev] Mixed C/C++ in MBS
> I think the biggest problem with this approach is that most projects
> will be using only C++ sources or only C sources,
I disagree with this assumption.
At Franklin we deal with 3rd party libraries from various vendors, some
are C some are C++, it is not uncommon to have a mix of glue code in
your
project. That GLUE is where the problems live.
This is *NO* different then having both 's' and 'S' files in a project.
I'm not at all suggesting for example Fortran in the same project, mixed
Fortran and C/C++ are very rare. Mixed C/C++ is very common and should
be supported.
Certainly, one can always "wrap" a C file in 'extern "C"' - but why
must I take out a pocket knife to make that fairly common square
peg fit in the round hole?
-Duane
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
