Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: mark.kettenis@xs4all.nl, Kai.Tietz@onevision.com,
	        gdb-patches@sourceware.org
Subject: Re: [RFC] convert a host address to a string
Date: Thu, 08 Jan 2009 13:12:00 -0000	[thread overview]
Message-ID: <200901081311.n08DBjg4006020@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20090108125430.GB20220@adacore.com> (message from Joel Brobecker 	on Thu, 8 Jan 2009 16:54:30 +0400)

> Date: Thu, 8 Jan 2009 16:54:30 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> 
> > Well, the PRIxxx macros are ISO C99 inventions, so we can't assume
> > they're generally available.  Guess that could be mitigated by
> > importing inttypes module from gnulib.
> 
> It's mentioned in the C90 draft document that I have. Has it been
> removed from the final revision?

Are you sure you're looking at a C90 draft and not a C99 draft?

The draft linked from the Wikipedia page:

    http://flash-gordon.me.uk/ansi.c.txt

doesn't mention <inttypes.h> or the PRIxPTR define.  I'm fairly sure
they're not part of C90, since the uintptr_t typedef isn't either.

> In any case, it doesn't work on Windows, because their definition
> is screwed. How about some of my suggestions?

Actually, I think their defenition is ok (but nonstandard).  IIRC,
%I64x is the way to print the __int64 type that Microsoft invented
before long long was standardized by C99.  So it seems the problem
here is with gcc.

I'll reply to your origional mail to discuss your alternative suggestions.


  parent reply	other threads:[~2009-01-08 13:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 12:19 Joel Brobecker
2009-01-07 16:17 ` Mark Kettenis
2009-01-08 10:19   ` Joel Brobecker
2009-01-08 10:25     ` Kai Tietz
2009-01-08 10:48       ` Joel Brobecker
2009-01-08 11:02         ` Kai Tietz
2009-01-08 11:25           ` Joel Brobecker
2009-01-08 11:31             ` Kai Tietz
2009-01-08 12:49           ` Mark Kettenis
2009-01-08 12:54             ` Joel Brobecker
2009-01-08 13:04               ` Kai Tietz
2009-01-08 13:12               ` Mark Kettenis [this message]
2009-01-08 13:26     ` Mark Kettenis
2009-01-08 13:35       ` Kai Tietz
2009-01-08 13:42         ` Joel Brobecker
2009-01-08 14:04           ` Kai Tietz
2009-01-08 16:18         ` Mark Kettenis
2009-01-08 16:23           ` Kai Tietz
2009-01-09  9:57             ` Joel Brobecker
2009-01-09 10:05               ` Kai Tietz
2009-01-09 13:12       ` Joel Brobecker
2009-01-09 14:28         ` Kai Tietz
2009-01-10  7:12           ` Joel Brobecker
2009-01-10 13:31             ` Kai Tietz
2009-01-10 13:34               ` Kai Tietz
2009-01-10 13:58               ` Mark Kettenis
2009-01-10 14:04               ` Mark Kettenis
2009-01-10 14:15                 ` Kai Tietz
2009-01-10 14:22                   ` Mark Kettenis
2009-01-10 14:25                     ` Kai Tietz
2009-01-11 13:31                     ` Joel Brobecker
2009-01-11 13:53                       ` Mark Kettenis
2009-01-13 12:09                     ` Joel Brobecker

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=200901081311.n08DBjg4006020@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=Kai.Tietz@onevision.com \
    --cc=brobecker@adacore.com \
    --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