delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2002/11/14/20:15:09

From: JMK <jeffrey DOT m DOT klopotic AT lmco DOT nospam DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: whats wrong with my compiler
Date: Thu, 14 Nov 2002 16:52:56 -0800
Organization: Lockheed Martin Corporation
Lines: 27
Message-ID: <3DD44568.141AB4FA@lmco.nospam.com>
References: <20021114225250 DOT 29569 DOT qmail AT web13001 DOT mail DOT yahoo DOT com>
NNTP-Posting-Host: 129.197.49.226
Mime-Version: 1.0
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Thomas,

The doctrine of backward compatiblity dictates that any compiler written
for a language be able to compile any previous code without
modification, proprietary extensions excepted.  Thus, a simple "Hello
World" type source must be recompilable on any version of compiler
design.  The presumption here is that we're talking C++ and that gcc
intends to be C++.  Further, it should be recompilable whether written
in C or C++.

If you what you assert is true, that one must now rewrite something as
simple as "Hello World" to meet new standards, my prediction is that
this oversight will be corrected once the economy gets going again.  All
those companies out there with legacy code that won't recompile are
going to be quite besides themselves once they find out just what
happened.  Either that, or C++ will be renamed D or whatever the next
generation will be called -- which is probably more appropriate.

In the meantime, you might want to advise to see if changing iostream to
iostream.h works.  If it does, a lot more people would be greatful if
you pointed out the historical change that occurred.  It will save a lot
of learning programmers a great deal of grief when realizing that it is
a system fault and not theirs.


Jeff

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019