Is it a good thing that program mix C and C++?

[dolphin]

Is it a good thing that program mix C and C++?

[Bill Pursell]

On 31 Mar, 07:29, Richard Heathfield <[e-mail].i nvalidwrote:

Malcolm McLean said:

I was converted to uncast malloc() by the ng. Not for the reason given
- that it can mask failure to include stdlib.h. In production code
that just can't happen.

When "just can't happen" relies on a basic level of human competence, we
can count on it happening at least 17 times a day, 260 days a year.

And 170 times a day the other 105.25 days. Emphasis on
"at least".

--
Bill Pursell

[Kenneth Brody]

Kenny McCormack wrote:
[...]

The point is that is you consider the following three commonly harped on
things in this NG:

1) char a[10]; x = a[10];
2) void main()
3) char *x = (char *) malloc(10);

The first is clearly an error. The 2nd probably, and the third, really not.
Yet all three are harped upon with equal vigor, by a bunch of freaks who
don't understand the concept of degree.

However, there are times when a newbie mentions that the reason
for putting the cast on malloc in the first place was to stop the
compiler from complaining about the int-to-pointer conversion.

While one might argue that the forgotten include won't happen in
"production code", the audience for clc is much wider than those
who write C for a living.

Yes, the cast is "harmless" if you have the proper #include. But,
it appears to be a relatively common newbie error to forget the
necessary #include, and they learned somewhere that you can "shut
up" the compiler by adding the cast, rather than by fixing the
root cause of the problem.

Now, I have an excuse for casting the return at times -- I learned
C in pre-void days, when the cast was necessary. Those days are
long gone, but old habits are hard to break. (Just try typing the
word "print" without a "f" magically appearing after it.)

--
+-------------------------+--------------------+-----------------------+
| Kenneth J. Brody | www.hvcomputer.com | #include |
| kenbrody/at\spamcop.net | www.fptech.com | <std_disclaimer .h|
+-------------------------+--------------------+-----------------------+
Don't e-mail me at: <mailto:Th***** ********@gmail. com>

[Dave Vandervies]

In article <46************ ***@spamcop.net >,
Kenneth Brody <ke******@spamc op.netwrote:

Those days are
long gone, but old habits are hard to break. (Just try typing the
word "print" without a "f" magically appearing after it.)

More than once, while writing English text, I've used the word "gets"
and then gone back to put an 'f' at the beginning.
dave

--
Dave Vandervies dj******@csclub .uwaterloo.ca
I try, and I'm just as quick to make a fool of myself as anybody.
Usually I don't make a complete fool of myself, but that happens too.
--Brendan Sechter in comp.lang.c

[Chris Hills]

In article <11************ *********@p15g2 000hsd.googlegr oups.com>,
dolphin <jd*******@gmai l.comwrites

>Is it a good thing that program mix C and C++?

If you mean in the same file NO.

If you mean can you call other modules written in C from a C++ program
then that is OK. Many libraries are written in C

However you should not be compelling C in a C++ compiler

C++ is based on C90 and has diverged one way whilst C99 went a
different way.

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ ch***@phaedsys. org www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

[Chris Hills]

In article <11************ **********@p15g 2000hsd.googleg roups.com>,
user923005 <dc*****@connx. comwrites

>On Mar 27, 9:41 pm, "dolphin" <jdxyw2...@gmai l.comwrote:

>Is it a good thing that program mix C and C++?

The C++ language includes the standard C libraries. Un

Not yet it doesn't TR not with standing.

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ ch***@phaedsys. org www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

[John Bode]

On Mar 27, 11:41 pm, "dolphin" <jdxyw2...@gmai l.comwrote:

Is it a good thing that program mix C and C++?

You certainly do *not* want to mix C and C++ idioms in the same source
file (e.g., using new to allocate memory and free() to deallocate it),
but you can certainly have different source files written in different
languages; you just have to pay attention to linkage rules and
parameter passing conventions.