Why does C/C++ use const & static so many times?

[Brian]

"Portability" doesn't mean that a C program
should also be a program in a different language.


It is common for a C++ compiler
to become a C compiler when compiling *.c files.

"pfft"

 

[Brian]

[...]
On one of our hardware platforms we have a C++ compiler but no C
compiler.

From time to time, it is a pain in the backside.

Easy fix: write a C compiler for that platform.

In The Beginning,

Ya think?

Wait, do tell us about "the beginning".

I said that wrong. What was that, a suggestion? You tell ME about this
"beginning" of yours.

"you talkin to me?". "hmm?". "Yeah you, ... you talkin to me?".

****************

Dude, twas a joke. I have comedy (but C is so funny I couldn't resist...
I'm not bad, you are).

 

[Brian]

[snip]

Perhaps, but (a) it's a C program written for C rules, not C++
rules, so a C compiler is indicated, and if you haven't got one the
right response is to get one; and (b) it is actually quite rare for
someone with a C++ compiler to be without a C compiler - so rare,
in fact, that I don't think I've ever encountered such a person.

I'd like to introduce myself, then. ;-)

Ha! There's always one, isn't there?

On one of our hardware platforms we have a C++ compiler but no C
compiler.

From time to time, it is a pain in the backside.

Easy fix: write a C compiler for that platform.

Or reject the pizza.

 

[Brian]

No, it's pronounced "Seebs", much like WATFIV is officially pronounced
"watt four".

I'm a consultant. It sounds like a "generational problem".

 

[Brian]

not totally general, but my experience with "toasters" (some of these
"toasters" were 10kw toasters) is being able to run most of the code
on a "proper" computer as well makes life easier. Sometimes the
"toasters" aren't available 'til late in the development cycle or
won't fit through the door. Of course this is all covered by your
"unless it has some value for *you*" clause.

Because you are an ass and don't know yourself from a hole in the ground.