From: Yao Qi <yao@codesourcery.com>
To: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [testsuite] Really ensure printf/fprintf are available in dprintf.exp
Date: Fri, 01 Jun 2012 13:13:00 -0000 [thread overview]
Message-ID: <4FC8BFE4.6@codesourcery.com> (raw)
In-Reply-To: <001801cd3ff6$de4fd150$9aef73f0$@muller@ics-cnrs.unistra.fr>
On 06/01/2012 09:02 PM, Pierre Muller wrote:
> I was just wondering if this is an expression that I do not know, or if
> you simply meant 'bare-metal'?
>
Hi Pierre,
I meant 'bare-metal'. It was a typo.
> Also, about the addition of
> +#include <stdlib.h>
> in the middle of the source, I also had the impression that
> traditionally, C sources group all include's at the top of the source,
> but remember that I only program in C for GDB and I am a pascal code
> developer otherwise...
Usually, if I include a header for a small piece of code, I prefer to
place the include near by my code. Otherwise, I'd like to put include
at the top of source. It is just my personal habit. Generally, either
should be OK.
--
Yao (é½å°§)
next prev parent reply other threads:[~2012-06-01 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 12:48 Yao Qi
2012-06-01 13:03 ` Pierre Muller
2012-06-01 13:13 ` Yao Qi [this message]
2012-06-06 8:55 ` [committed]: " Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FC8BFE4.6@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox