🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.java
Article #247

Re: Will Java kill C++?

#247
From: David James Hanley
Date: Sun, 14 Apr 1996 23:05
95 lines
4938 bytes
Andrew Koenig (ark@research.att.com) wrote:
: In article <4kn3c4$1ggc@piglet.cc.uic.edu> dhanle2@icarus.cc.uic.edu (David James Hanley) writes:
: > andrek koenig wrote:

: Is your transformation of my name supposed to be clever?
: To make you feel like a better, more noble person?
: To make your arguments more intellectually compelling?
: To show the world that you enjoy insulting strangers?

	No, actually, when I was trimming the post, I accidentally 
clipped off your name, and made a typo when I typed it back in.  
I realize that mistyping your name is a mortal sin to the god of c++,
even if he projects his like for flaming strangers onto others.

: > : The thing about hurling expletives around like that
: > : is that it's so embarrassing when you're wrong -- as
: > : you are in this case.

: > 	Or that he is correct, as he is in this case.

: Correct about what?  That having a name-mangling standard for C++
: would make C++ libraries easier to handle.  Sorry, but he's wrong,
: and so are you.

	Nope. You're the one who is wrong here.  But seeing as you
replied to my first post about the matter with insults to me, I really
doubt you are interested in serious exploration of the matter.  But
hurling childish insults.

: Name mangling, that is, the conventions that a compiler uses
: in translating names from the source program into names
: that the linker sees, is only one of a large number of things
: that must be agreed before programs compiled with one compiler
: can be linked with programs compiled with another.

	Sure.  No one is saying anything different.  Name mangling
if only one of the obstacles to be overcome.  But many of these other
obstacles have been overcome on other platforms already.  It appears to
be somewhat stupid to make yet more obstacles by failing to standardize
something as simple as name mangling.

:  If some
: of those things are made compatible and not others, that can
: easily make the problems worse instead of better.

	How can it be worse than not working at all?  

:  The reason
: is that programs may appear to work compatibly when in fact
: they are working only by accident.

	Remind me to throw away all of my C programs in that case--they
a are all linked with a library compiled on a different compiler, 
and are therefore broken.  Pity.

: Well, good for you.  That still does not gainsay the fact that
: handing the same names to the linker does not make compilers
: compatible.

	No, and again, no one said it did.  But a lot of work has been
done to allow link-compatibility within C libraries.  It seems foolish
to throw this all away.

: > : Getting a single binary library to work with both those
: > : C compilers is no easier than it is in C++.

: > 	Wrong.  As evidence, we do this all the time in C,
: > but I've never seen it done in C++. 

: I completely agree with you that link compatibility between C++
: compilers is more difficult to achieve, hence less common, than
: link compatibility between C compilers.

	Whups!  A few lines above you said it was no easier!

: But agreeing on a standard for name mangling would not solve that
: problem, because it is vanishingly rare that two C++ compilers are
: binary compatible in all details except for names.

	Right.  Since the name mangling is unspecified, why stick to the
standard techniques for the platform?  We can squeeze out another 5% of
performance by passing the first paramater as a register( or whatever ).
Binary incompatibility between compilers is a serious problem, for sharing
of libraries, and other such activities, and it sure would help things
if the committee could have put it in the standard, removing yet one
more problem.  I mean, they added literal "and" and "or" for bob's sake.

--
------------------------------------------------------------------------------
David Hanley,                 |______     Computer Science graduate student.  
dhanley@lac.eecs.uic.edu      |\ ___/__  Martial Artist. Biker. Chess Freak   
www_lac.eecs.uic.edu/~dhanley/| \\ /  / Libertarian.  Atheist.  Bisexual.     
My employer barely KNOWS me.  |  \/BI/ Aspiring novelist.Joyce Kafka Neitzchie
-----------------------------------\/-----------------------------------------
Hemlock? I never touch the stuff!
Technical Details
Message-ID: <4ks0c8$jte@piglet.cc.uic.edu>
Path: arc1-ca.pugleaf.net!news.cc.uic.edu!icarus!dhanle2
References: <31683229.446B9B3D@bbn.com> <DpJs8I.8tn@research.att.com> <4kn3c4$1ggc@piglet.cc.uic.edu> <Dpt0FD.Et4@research.att.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!news.cc.uic.edu!icarus!dhanle2
From: dhanle2@icarus.cc.uic.edu (David James Hanley)
Newsgroups: comp.lang.java,comp.lang.c++,comp.lang.smalltalk
Subject: Re: Will Java kill C++?
Followup-To: comp.lang.java,comp.lang.c++,comp.lang.smalltalk
Date: 14 Apr 1996 23:05:44 GMT
Organization: University of Illinois at Chicago
Message-ID: <4ks0c8$jte@piglet.cc.uic.edu>
References: <31683229.446B9B3D@bbn.com> <DpJs8I.8tn@research.att.com> <4kn3c4$1ggc@piglet.cc.uic.edu> <Dpt0FD.Et4@research.att.com>
NNTP-Posting-Host: icarus.cc.uic.edu
X-Newsreader: TIN [version 1.2 PL2]