kopia lustrzana https://gitlab.com/sane-project/website
135 wiersze
5.3 KiB
HTML
135 wiersze
5.3 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>sane-devel: Re: sane and gcc 2.96</TITLE>
|
|
<META NAME="Author" CONTENT="Paul Floyd (paulf@free.fr)">
|
|
<META NAME="Subject" CONTENT="Re: sane and gcc 2.96">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|
<H1>Re: sane and gcc 2.96</H1>
|
|
<!-- received="Mon Nov 20 07:47:59 2000" -->
|
|
<!-- isoreceived="20001120154759" -->
|
|
<!-- sent="Mon, 20 Nov 2000 17:03:12 +0100 (MET)" -->
|
|
<!-- isosent="20001120160312" -->
|
|
<!-- name="Paul Floyd" -->
|
|
<!-- email="paulf@free.fr" -->
|
|
<!-- subject="Re: sane and gcc 2.96" -->
|
|
<!-- id="974736192.3a194b4073cdb@imp.free.fr" -->
|
|
<!-- inreplyto="20001120160023Z.rene@jackson" -->
|
|
<STRONG>From:</STRONG> Paul Floyd (<A HREF="mailto:paulf@free.fr?Subject=Re:%20sane%20and%20gcc%202.96&In-Reply-To=<974736192.3a194b4073cdb@imp.free.fr>"><EM>paulf@free.fr</EM></A>)<BR>
|
|
<STRONG>Date:</STRONG> Mon Nov 20 2000 - 08:03:12 PST
|
|
<P>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0279.html">Oliver Rauch: "Re: scanimage-files in frontend package"</A>
|
|
<UL>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0277.html">Rene Rebe: "Re: sane and gcc 2.96"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0277.html">Rene Rebe: "Re: sane and gcc 2.96"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0268.html">Henning Meier-Geinitz: "Re: sane and gcc 2.96"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#278">[ date ]</A>
|
|
<A HREF="index.html#278">[ thread ]</A>
|
|
<A HREF="subject.html#278">[ subject ]</A>
|
|
<A HREF="author.html#278">[ author ]</A>
|
|
</UL>
|
|
<HR NOSHADE><P>
|
|
<!-- body="start" -->
|
|
<P>
|
|
Quoting Rene Rebe <<A HREF="mailto:rene.rebe@gmx.net?Subject=Re:%20sane%20and%20gcc%202.96&In-Reply-To=<974736192.3a194b4073cdb@imp.free.fr>">rene.rebe@gmx.net</A>>:
|
|
<BR>
|
|
<P><EM>> Could you explain me (or us) how you got to these prehistoric opinion
|
|
</EM><BR>
|
|
<EM>> about c++?? There IS the ANSI C++ standard. And writing good c++ code
|
|
</EM><BR>
|
|
<EM>> leads directly to well organized and maintainable programs! - Not
|
|
</EM><BR>
|
|
<EM>> compareable with the trange spaghetti code in much c-programs. And
|
|
</EM><BR>
|
|
<EM>> even if there would be different c++ "standards" I simply would take
|
|
</EM><BR>
|
|
<EM>> gcc's g++ ...
|
|
</EM><BR>
|
|
<P>Let me start by saying that, on the whole I prefer C++ to C.
|
|
<BR>
|
|
<P>As far as interoperability is concerned, C++ is a catastrophe. Just because
|
|
<BR>
|
|
there is a standard doesn't make the C++ compilers interoperable (since the
|
|
<BR>
|
|
"standard" doesn't set down any hard rules for linkage). Thus, your code may be
|
|
<BR>
|
|
well organized and maintainable as long as you stick to the same compiler. It
|
|
<BR>
|
|
seems from the previous comments that the latest version of g++ is not even
|
|
<BR>
|
|
backwards compatible with older versions.
|
|
<BR>
|
|
<P>If you want, you can try to figure out how each one mangles names, and the
|
|
<BR>
|
|
calling convention for each one. Then if your lucky you might get object code
|
|
<BR>
|
|
from one C++ compiler to link with object code from another. The alternative, if
|
|
<BR>
|
|
you have the source code available, is to migrate it to the other compiler. In
|
|
<BR>
|
|
the future, when all compilers are more or less ANSI/ISO compliant (and note
|
|
<BR>
|
|
again that there are plenty of things that the standard says are "up to the
|
|
<BR>
|
|
compiler vendor"), then that might not be a big problem. However, porting
|
|
<BR>
|
|
between 2 C++ compilers that have an age gap of say 5 years won't be that
|
|
<BR>
|
|
straightforward.
|
|
<BR>
|
|
<P>C (and this was the point that was being made) generates object code that can be
|
|
<BR>
|
|
linked to with almost universal ease. Even interpreted languages link easily to
|
|
<BR>
|
|
C object code.
|
|
<BR>
|
|
<P>There are large research projects into how to tackle the enormous problems of
|
|
<BR>
|
|
"legacy OO code" (mainly C++).
|
|
<BR>
|
|
<P>A bientot
|
|
<BR>
|
|
Paul
|
|
<BR>
|
|
<PRE>
|
|
--
|
|
Paul Floyd <A HREF="http://paulf.free.fr">http://paulf.free.fr</A> for those with time to waste
|
|
What's the point? The sharp thing on the end.
|
|
<P>--
|
|
Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20sane%20and%20gcc%202.96&In-Reply-To=<974736192.3a194b4073cdb@imp.free.fr>">majordomo@mostang.com</A>
|
|
</PRE>
|
|
<P><!-- body="end" -->
|
|
<HR NOSHADE>
|
|
<UL>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0279.html">Oliver Rauch: "Re: scanimage-files in frontend package"</A>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0277.html">Rene Rebe: "Re: sane and gcc 2.96"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0277.html">Rene Rebe: "Re: sane and gcc 2.96"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0268.html">Henning Meier-Geinitz: "Re: sane and gcc 2.96"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#278">[ date ]</A>
|
|
<A HREF="index.html#278">[ thread ]</A>
|
|
<A HREF="subject.html#278">[ subject ]</A>
|
|
<A HREF="author.html#278">[ author ]</A>
|
|
</UL>
|
|
<!-- trailer="footer" -->
|
|
<HR NOSHADE>
|
|
<P>
|
|
<SMALL>
|
|
<EM>
|
|
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
|
|
: <EM>Mon Nov 20 2000 - 07:48:19 PST</EM>
|
|
</EM>
|
|
</SMALL>
|
|
</BODY>
|
|
</HTML>
|