X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
Date: Thu, 15 Jan 2004 11:45:36 +0200 (EET)
From: Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Sender: peuha AT sirppi DOT helsinki DOT fi
To: djgpp-workers AT delorie DOT com
Subject: Re: Use of FILE in sprintf/sscanf
In-Reply-To: <u4quzwyc5.fsf@elta.co.il>
Message-ID: <Pine.OSF.4.58.0401151136500.19575@sirppi.helsinki.fi>
References: <Pine DOT OSF DOT 4 DOT 58 DOT 0401051334160 DOT 4628 AT sirppi DOT helsinki DOT fi> 
 <4002FE15 DOT 8040707 AT phekda DOT gotadsl DOT co DOT uk> <Pine DOT OSF DOT 4 DOT 58 DOT 0401131249170 DOT 16534 AT sirppi DOT helsinki DOT fi>
 <u4quzwyc5 DOT fsf AT elta DOT co DOT il>
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 Tue, 13 Jan 2004, Eli Zaretskii wrote:

> I was mainly concerned with having code on header files; debugging
> problems is only one of the headaches it brings.

What kind of other problems does it cause?  (I can't remember ever
reading about any that aren't related to debugging.)

> You cannot easily put a breakpoint or step thru such functions, and

Why would you expect to?  In my opinion, inlined functions should be
considered similar to macros in this respect.

> COFF debug info doesn't support included code at all.

That's not really true: COFF files are quite capable of handling any
number of source files per one object file (the DJGPP FAQ 12.6 is
simply wrong), because clearly DJGPP programs (which are just COFF
files) can have more than one source file and still contain proper
debug info.  If GCC and GAS can't produce the proper debug info for
included source files, that's a bug in them.

-- 
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/