From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] Formats %H, $<, %[ (Was re. ratrace problem; debuggers welcome)
Date: Mon, 14 Feb 2011 07:45:16 -0500 [thread overview]
Message-ID: <4D5923DC.2090201@gmail.com> (raw)
In-Reply-To: <781726dc6db5b2735c3d62e92d46c44d@chula.quanstro.net>
On 02/14/2011 01:03 AM, erik quanstrom wrote:
> that doesn't really work for me. either the kernel should always print
> as hex, or the decision should be made for the whole string. the \x
> notation requires that any \x be excaped. you potentially need to escape
> both " and \. it's a difficult and non-standard quoting scheme for plan 9.
> if you think the kernel really needs to be making a decision based on
> utf-8/not utf-8 (not 7-bit ascii!), i would think the most standard way
> of formatting this would be nil, %.*q or %.*H.
I remembered reading of, and using, the %q format, but %H is new to me.
The web version of print(2) doesn’t describe it, so I went to the source.
In libc.h I found
#pragma varargck type "<" void*
#pragma varargck type "[" void*
#pragma varargck type "H" void*
#pragma varargck type "lH" void*
but none of these are in the knownfmt[] array in sys/src/libc/fmt/fmt.c
and I don’t see where fmtinstall() is called for them.
What do these formats do?
--Joel
next prev parent reply other threads:[~2011-02-14 12:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 0:32 [9fans] ratrace problem; debuggers welcome ron minnich
2011-02-14 3:50 ` erik quanstrom
2011-02-14 4:40 ` ron minnich
2011-02-14 6:03 ` erik quanstrom
2011-02-14 12:45 ` Joel C. Salomon [this message]
2011-02-14 12:48 ` [9fans] Formats %H, $<, %[ (Was re. ratrace problem; debuggers welcome) erik quanstrom
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=4D5923DC.2090201@gmail.com \
--to=joelcsalomon@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).