public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, sezeroz@gmail.com, tromey@redhat.com
Subject: Re: [PATCH] [Windows] fix format string for 64 bit var in gdbserver
Date: Sat, 17 Jul 2010 18:49:00 -0000	[thread overview]
Message-ID: <201007171446.08501.vapier@gentoo.org> (raw)
In-Reply-To: <201007171228.o6HCSnd8017188@glazunov.sibelius.xs4all.nl>

[-- Attachment #1: Type: Text/Plain, Size: 466 bytes --]

On Saturday, July 17, 2010 08:28:49 Mark Kettenis wrote:
> From: Mike Frysinger <vapier@gentoo.org>
> > ugh, no.  why not use a sane define like PRIx64 from inttypes.h ?
> 
> "sane" isn't the word I'd use.  Not only do I find them to make printf
> format strings to become unreadable, they also cause i18n issues.

the former is debatable, and while the latter is a valid point in the general 
case, i18n issues in this particular case do not apply.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2010-07-17 18:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16 20:10 Ozkan Sezer
2010-07-17  9:40 ` Mike Frysinger
2010-07-17  9:42   ` Ozkan Sezer
2010-07-17  9:53     ` Ozkan Sezer
2010-07-17 18:50       ` Mike Frysinger
2010-07-17 18:59         ` Ozkan Sezer
2010-07-17 19:19           ` Mike Frysinger
2010-07-17 19:23             ` Ozkan Sezer
2010-07-17 21:01           ` Andreas Schwab
2010-07-17 21:05             ` Ozkan Sezer
2010-07-20 18:20               ` Ozkan Sezer
2010-07-17 12:29   ` Mark Kettenis
2010-07-17 18:49     ` Mike Frysinger [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=201007171446.08501.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=sezeroz@gmail.com \
    --cc=tromey@redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).