From: "Noam Preil" <noam@pixelhero.dev>
To: <9front@9front.org>
Subject: Re: [9front] Re: cc: support binary constants and refactor
Date: Wed, 28 Jun 2023 01:06:16 -0400 [thread overview]
Message-ID: <CTO0TAXZ58WO.3304KHG03LRHD@navani.radiant.pixelhero.dev> (raw)
In-Reply-To: <BCAFF6B66C40C79524ADFD7C6A6D0C3D@eigenstate.org>
I third this.
I don't find myself reaching for them often, but it's sometimes nice
when e.g. working on an emulator to be able to specify bitflags as a
binary string instead of hex; it makes it easier to decode what the heck
the flags are actually being set to, for instance!
It breaks nothing, is standardized, eases porting, and is occasionally
useful; why not add it?
next prev parent reply other threads:[~2023-06-28 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 6:26 qwx
2023-06-27 12:38 ` Jacob Moody
2023-06-27 21:57 ` qwx
2023-06-28 0:15 ` Jacob Moody
2023-06-28 0:45 ` qwx
2023-06-28 1:28 ` Jacob Moody
2023-06-28 1:48 ` ori
2023-06-28 5:06 ` Noam Preil [this message]
2023-06-30 20:25 ` hiro
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=CTO0TAXZ58WO.3304KHG03LRHD@navani.radiant.pixelhero.dev \
--to=noam@pixelhero.dev \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).