unionists versus separatists

[E. Robert Tisdale]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

Radical separatist write C codes that C++ compilers won't accept.
Radical unionists insist that C will eventually adopt
all of the semantics of C++.

Does C really have a future separate from C++?
Will all C programmers eventually abandon C for C++?
Or will the race of C programmers eventually die out?

 

[James Hu]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

Radical separatist write C codes that C++ compilers won't accept.
Radical unionists insist that C will eventually adopt
all of the semantics of C++.

Does C really have a future separate from C++?
Will all C programmers eventually abandon C for C++?
Or will the race of C programmers eventually die out?

How about rephrasing your query with "assembly language" in place of C, and
with C in place of C++?

-- James

 

[Richard Heathfield]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

Three camps, at least. You forgot all about those who don't give a damn what
C++ does, because C and C++ are separate languages.

Radical separatist write C codes that C++ compilers won't accept.

Don't be silly. I write C code that COBOL compilers won't accept. Does that
make me a radical separatist with respect to COBOL and C? Of course not.

Radical unionists insist that C will eventually adopt
all of the semantics of C++.

If you want C++, you know where to find it.

Does C really have a future separate from C++?
Yes.

Will all C programmers eventually abandon C for C++?
No.

Or will the race of C programmers eventually die out?

Unlikely.

 

[Papadopoulos Giannis]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

Radical separatist write C codes that C++ compilers won't accept.
Radical unionists insist that C will eventually adopt
all of the semantics of C++.

Does C really have a future separate from C++?
Will all C programmers eventually abandon C for C++?
Or will the race of C programmers eventually die out?

I program in C, though I hate for the time being anything that has to do
with C++... I am not a separist, I simply don' t like C++.. I try to
perfect my C code as a C code, not as a C++ code...

PS For OOP, I like Java more (don't start a flame war plzzz)...

 

[Richard Heathfield]

I program in C, though I hate for the time being anything that has to do
with C++... I am not a separist, I simply don' t like C++.. I try to
perfect my C code as a C code, not as a C++ code...

PS For OOP, I like Java more (don't start a flame war plzzz)...

What do you think he was trying to start - a cosy little chat?

Mr Tisdale is a known troll. Best avoided if possible. I don't know of any C
experts who consider Mr Tisdale's opinions on C to be worth much (except in
cases where those opinions accidentally collide with good practice, which
is rare)[1]. If you're new to the language, you'd be far better off reading
articles by genuine experts, such as Chris Torek, Dan Pop (although the
latter can be a bit acerbic at times), Dik Winter, Jeremy Yallop, Christian
Bau, Jack Klein, Ben Pfaff, etc.



[1] A notable exception is the malloc-casting issue where, for reasons of
his own, the well-respected Mr Plauger happens to share an unpopular
opinion with Mr Tisdale.

 

[Nils Petter Vaskinn]

C programmers appear to be divided into two camps:
1. unionists who want to draw C and C++ closer together and 2.
separatist who want draw C farther away from C++.

What makes you think this? I have seen people wanting specific C++
features in C, but I've never seen anyone argue that C should/will evolve
into C++. It won't happen because there is no need for C to become C++
since we've already got C++.

Radical separatist write C codes that C++ compilers won't accept.

Because you compile C as C and not C++. That shouldn't prevent a C++
program from beeing linked against C code, so what is the purpose of
writing C for C++ compilers.

Radical unionists insist that C will eventually adopt all of the
semantics of C++.

What is the point? If they think C should be C++ why don't they simply use
C++?

Does C really have a future separate from C++? Yes.

Will all C programmers eventually abandon C for C++?

No. They might use both. You don't throw away your screwdriver because
you've got a brand new hammer.

Or will the race of C programmers eventually die out?

Not in our lifetime.

 

[Richard Bos]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

3. Realists who know that C++ already is a different language from C,
and don't much care whether they grow closer or further away.

Radical separatist write C codes that C++ compilers won't accept.
Radical unionists insist that C will eventually adopt
all of the semantics of C++.

Realists write proper C code, without regard _or_ disregard of what a
C++ compiler accepts. It's C, not C++.

Does C really have a future separate from C++?

Of course.

Will all C programmers eventually abandon C for C++?

Don't be daft.

Or will the race of C programmers eventually die out?

Sure. So will the race of human beings.

Richard

 

[Martin Dickopp]

I program in C, though I hate for the time being anything that has

^^^^

to do with C++... I am not a separist, I simply don' t like C++..

Strange that people often have such strong emotions about programming
languages...

I use C, C++, and various other languages, and I don't choose which
language to use for a specific problem by liking, but by which language
I think is the best tool for the job.

Just my 0.02,
Martin

 

[gswork]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

Radical separatist write C codes that C++ compilers won't accept.
Radical unionists insist that C will eventually adopt
all of the semantics of C++.

Does C really have a future separate from C++?
Will all C programmers eventually abandon C for C++?
Or will the race of C programmers eventually die out?

Oh, I thought you were going to talk about unions v structs (a union
of mutually exclusive data, or seperation into defined, unshared,
parts of a struct)

Well, I like structs! I don't think C and C++ are, or need be,
mutually exclusive.

I suspect what really matters is what the ISO people are advised and
consider.

 

[Kral Vendar]

Mr Tisdale is a known troll. Best avoided if possible. I don't know of any
C

experts who consider Mr Tisdale's opinions on C to be worth much (except in
cases where those opinions accidentally collide with good practice, which
is rare)[1]. If you're new to the language, you'd be far better off reading
articles by genuine experts, such as Chris Torek, Dan Pop (although the
latter can be a bit acerbic at times), Dik Winter, Jeremy Yallop, Christian
Bau, Jack Klein, Ben Pfaff, etc.

You should read a good article about net etiquete before posting on usenet.
Leave your personal opinions about other posters out of this place.

 

[pete]

Richard Heathfield wrote:

Mr Tisdale is a known troll. Best avoided if possible.
I don't know of any C experts who consider Mr Tisdale's
opinions on C to be worth much
(except in cases where those opinions accidentally
collide with good practice, which is rare)[1].

You can't guess wrong all the time.
You have to know everything, to be wrong all the time.

 

[Mark A. Odell]

Will all C programmers eventually abandon C for C++?

No. Implement a complete C run-time on an 8051, PIC, MSP420, AVR, or some
other 8-bit micro. Then try writing a C++ run-time - oops, out of CPU
resource, game over.

 

[CBFalconer]

Mr Tisdale is a known troll. Best avoided if possible. I don't
know of any C experts who consider Mr Tisdale's opinions on C
to be worth much (except in cases where those opinions
accidentally collide with good practice, which is rare)[1]. If
you're new to the language, you'd be far better off reading
articles by genuine experts, such as Chris Torek, Dan Pop
(although the latter can be a bit acerbic at times), Dik
Winter, Jeremy Yallop, Christian Bau, Jack Klein, Ben Pfaff,
etc.

You should read a good article about net etiquete before posting
on usenet. Leave your personal opinions about other posters out
of this place.

You might search the archives for Tisdale (aka Trollsdale)
mouthings before criticizing such good advice. Then you might set
your reader to preserve attribution lines.

 

[Richard Heathfield]

Mr Tisdale is a known troll. Best avoided if possible. I don't know of
any C
experts who consider Mr Tisdale's opinions on C to be worth much (except in
cases where those opinions accidentally collide with good practice, which
is rare)[1]. If you're new to the language, you'd be far better off reading
articles by genuine experts, such as Chris Torek, Dan Pop (although the
latter can be a bit acerbic at times), Dik Winter, Jeremy Yallop, Christian
Bau, Jack Klein, Ben Pfaff, etc.

You should read a good article about net etiquete before posting on
usenet. Leave your personal opinions about other posters out of this
place.

Total number of articles posted to comp.lang.c by Kral Vendar: 1
Of those: number of articles discussing the C language: 0
number of articles hostilely addressing an individual: 1

When Mr Vendar has established a history of posting useful advice about C on
this newsgroup, maybe I'll pay more attention to his opinions. Of course,
by then, he'll have discovered for himself that Tisdale is a troll and,
when he says so, no doubt some newbie or other will attack /him/ for so
doing.

Round and round and round.

 

[John Bode]

C programmers appear to be divided into two camps:

1. unionists who want to draw C and C++ closer together and
2. separatist who want draw C farther away from C++.

The hell? Why do I feel like I'm in Northern Ireland? Or Quebec?

Radical separatist write C codes that C++ compilers won't accept.

Given that C's and C++'s semantics differ in some key areas, sometimes
it's kind of hard to avoid writing C code that doesn't compile as C++.

Radical unionists insist that C will eventually adopt
all of the semantics of C++.

Radical unionists are morons and/or trolls. Why make C exactly like
C++? What is the point in having two separate languages that are
alike? Should C# also adopt all the semantics of C++? How about
Java? Maybe Visual Basic should also be exactly like C++?

Here's a thought: maybe these "radical unionists" should just use C++
and not worry about C at all. I think everyone would be happier.

Does C really have a future separate from C++?

In the long, ignominious history of stupid questions, this one stands
out.

Will all C programmers eventually abandon C for C++?
No.

Or will the race of C programmers eventually die out?

Well, duh. I doubt anyone's going to be programming in C a thousand
years from now.

 

[Alan Balmer]

Mr Tisdale is a known troll. Best avoided if possible. I don't know of any C
experts who consider Mr Tisdale's opinions on C to be worth much (except in
cases where those opinions accidentally collide with good practice, which
is rare)[1]. If you're new to the language, you'd be far better off reading
articles by genuine experts, such as Chris Torek, Dan Pop (although the
latter can be a bit acerbic at times), Dik Winter, Jeremy Yallop, Christian
Bau, Jack Klein, Ben Pfaff, etc.

You should read a good article about net etiquete before posting on usenet.
Leave your personal opinions about other posters out of this place.

Those are not "personal" opinions about posters, they are professional
opinions about what those posters write, and are shared by many
(almost all) the professionals who frequent this newsgroup.

 

[Martin Ambuhl]

You should read a good article about net etiquete before posting on usenet.
Leave your personal opinions about other posters out of this place.

This is surely a mistaken view. ERT is well-known for providing incorrect
"answers" and doing so with the strong position that anyone posting
actually correct answers is a fool. We owe it to unwary posters to warn
them that ERT's views must be *heavily* discounted and that his bluster is
empty wind to hide the fact that he knows nothing about the subject on
which he pretends to be expert.

 

[Default User]

Richard Heathfield wrote:

Mr Tisdale is a known troll. Best avoided if possible. I don't know of any C
experts who consider Mr Tisdale's opinions on C to be worth much (except in
cases where those opinions accidentally collide with good practice, which
is rare)[1].

In large part, knowlegable C++ people don't consider his opinions on
that language to be worthwhile either. He likes to troll, plain and
simple.



Brian Rodenborn

 

[E. Robert Tisdale]

Take a look at:

C and C++: Case Studies in Compatibility by Bjarne Stroustrup

http://www.cuj.com/documents/s=8009/cuj0209stroustr/

 

[Arthur J. O'Dwyer]

Not in our lifetime.

Brilliant! ;-)

-Arthur,
but please don't feed the trolls anyway