From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Add support for catch Ada exceptions (take 2)
Date: Tue, 02 Jan 2007 14:34:00 -0000 [thread overview]
Message-ID: <20070102143420.GB10603@nevyn.them.org> (raw)
In-Reply-To: <20070102054523.GF17211@adacore.com>
On Tue, Jan 02, 2007 at 09:45:23AM +0400, Joel Brobecker wrote:
> I prefer this solution over using xsnprintf as suggested by Mark,
> because we then introduce an arbitrary constant. But it's only a mild
> preference, however, so let me know if you prefer it like this:
>
> char msg[512];
> xsnprintf (msg, sizeof (msg), _("`%s' Ada exception"), b->addr_string);
You could use xstrprintf instead.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-02 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 6:06 Joel Brobecker
2006-12-31 21:59 ` Eli Zaretskii
2006-12-31 22:11 ` Mark Kettenis
2007-01-02 5:44 ` Joel Brobecker
2007-01-02 13:27 ` Andreas Schwab
2007-01-02 14:34 ` Daniel Jacobowitz [this message]
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=20070102143420.GB10603@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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