Date: Mon, 19 Mar 2001 15:44:00 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: pavenis AT lanet DOT lv
cc: djgpp-workers AT delorie DOT com
Subject: Re: About release of gcc-2.95.3 for DJGPP
In-Reply-To: <3AB61398.19432.C52D4E@localhost>
Message-ID: <Pine.SUN.3.91.1010319154135.24078D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 19 Mar 2001 pavenis AT lanet DOT lv wrote:

> > > gcov generates name of output file by appending to name ".gcov".
> > > So for foo.c we're getting foo.c.gcov. 
> > 
> > Making foo.gcov would probably solve this.
> 
> Perhaps not so.  foo.c and foo.h may both contain code (the second - 
> some inline functions)

Right.  Then it has to be something more complicated, like this:

	foo.c -> foo.cgcov
	foo.h -> foo.hgcov
	foo.cc -> foo.ccgcov
	foo.cpp -> foo.cpgcov

That is, leave at least the leading `g' of `gcov' in the extension, 
eating up the original extension as needed.