From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9fans@9fans.net
Subject: Re: [9fans] uvlong does not work on 9legacy raspberry pi image
Date: Mon, 19 May 2025 19:37:50 -0400 [thread overview]
Message-ID: <ff885c4d-8414-4154-9f36-69495251d20b@fjrhome.net> (raw)
In-Reply-To: <9f406cbd-623c-4772-ad00-7fb15605260d@sirjofri.de>
In standard C, the "u" replaces the "d", so no, I didn't mix it up.
That is, of course, unless the Plan 9 C compilers require using
nonstandard format specifiers for unsigned integers - to be honest, I
haven't really checked that.
On 5/19/25 06:35, sirjofri via 9fans wrote:
> 19.05.2025 11:06:20 Frank D. Engel, Jr. <fde101@fjrhome.net>:
>> Just to point it out, you should technically be using %llu instead of %lld for an unsigned value, though that would not explain the problems described here.
> Are you sure you don't mix this up with %ulld?
>
> Idk, I never used scanf on plan 9. I can imagine that using the proper format fixes the problems, though I also don't fully understand why the problems occur like they're described.
>
> sirjofri
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T3df06e15ad1bc104-M955764cad20ccad45e3a8cda
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
prev parent reply other threads:[~2025-05-20 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 5:14 hahahahacker2009
[not found] ` <6217A342E4752D83738A502BE6EDD751@eigenstate.org>
2025-05-19 15:25 ` Ori Bernstein
[not found] ` <ffeeafae-605d-45e6-aa42-951535b717f9@fjrhome.net>
[not found] ` <9f406cbd-623c-4772-ad00-7fb15605260d@sirjofri.de>
2025-05-19 23:37 ` Frank D. Engel, Jr. [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=ff885c4d-8414-4154-9f36-69495251d20b@fjrhome.net \
--to=fde101@fjrhome.net \
--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).