public inbox for
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <>
To: "" <>
Subject: RE: [EXTERNAL] Re: [PATCH 2/7] Use matching format for NTSTATUS
Date: Sun, 16 Jan 2022 00:20:03 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> Just the suggestion that as all standards support using %#08x to prefix
> with 0x (prefix output capitalization follows format letter
> capitalization) and would be preferable to hacking the text 0x onto the
> format %08X, doing all of the formatting work with the format flags.

First off, I am perfectly aware of the "alternate" form, and I don't like it
because it either creates all-caps representation (which I find hard to read,
and I mentioned that), or it creates a "camel-case" representation (all "normal"
digits are "capital" letters, while a-f are not, and I do not like that,

> My awareness and attitude to modifying output presentation using only
> formats was hardened by those not using date formats to modify date
> presentation during projects prior to Y2K!

It may be so but it has nothing to do with the output of NT status here.

Also, a little tolerance of how something can be done not exactly the way
you would do it, goes a long way.

Thank you for not trolling,

Anton Lavrentiev
Contractor NIH/NLM/NCBI

  reply	other threads:[~2022-01-16  0:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 22:10 Cygwin: A few fixes for local resolver Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 1/7] Fix format specifier for wide-char string Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 2/7] Use matching format for NTSTATUS Anton Lavrentiev
2022-01-15  4:38   ` Brian Inglis
2022-01-15 19:04     ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-01-15 22:38       ` Brian Inglis
2022-01-16  0:20         ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2022-01-14 22:10 ` [PATCH 3/7] Debug output to show both IP and port # in native b.o., a few little cosmetic improvements for consistency Anton Lavrentiev
2022-01-17 10:39   ` Corinna Vinschen
2022-01-17 10:44     ` Corinna Vinschen
2022-01-14 22:10 ` [PATCH 4/7] Process options forward (not backwards) Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 5/7] Format consitency for Windows errors Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 6/7] Message consistency Anton Lavrentiev
2022-01-14 22:10 ` [PATCH 7/7] Added processing of AAAA records Anton Lavrentiev

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).