Date: Mon, 15 Dec 1997 16:17:53 +0100 (MET)
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp workers list <djgpp-workers AT delorie DOT com>
Subject: Re: Trouble with C++ and interrupt (fwd)
In-Reply-To: <Pine.SUN.3.91.971215103351.22478F-100000@is>
Message-ID: <Pine.LNX.3.93.971215161122.9550A-100000@acp3bf>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

On Mon, 15 Dec 1997, Eli Zaretskii wrote:
[on making 'ld' find -lstdcxx -liostream automagically...]
> It seems that something like %{.cc: -lstdcxx -liostream} (and the same
> for other C++ suffixes) in the "*link_command:" section should do the
> job.

Sorry, but it almost certainly won't, as most C++ programs will be
multi-file ones, and so they usually won't be compiled and linked in one
go, but instead the linker run will be passed a list of .o files only,
which are indistinguishable from compiled C (or F77, or Pascal, or
whatever) files.

Now, imagine the surprise on the users' side when the compiler suddenly
stops to work automagically as soon as exercise #4 or so of their C++
book tells them to split their program in several sources and compile
it again. :-(

I doubt there's any real way against this but retro-moderation of the
newsgroup, combined with a fully automated reply-generator for this kind
of questions. Kind of like a 'FAQ-o-matic' with automatic cancellation of
articles built into it. 

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.