From: Jason Bowen <jbowen@infinitecactus.com>
To: tuhs@tuhs.org, Larry McVoy <lm@mcvoy.com>, Clem Cole <clemc@ccc.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Revisiting 6th Edition: rxv64
Date: Mon, 01 May 2023 22:05:22 -0500 [thread overview]
Message-ID: <C9773FDA-880A-48AB-8845-5CF8CC492C98@infinitecactus.com> (raw)
In-Reply-To: <20230502023451.GK29744@mcvoy.com>
Love the comment above main()
> /// Starting an operating system is inherently unsafe.
https://github.com/dancrossnyc/rxv64/blob/c19418398de24e55f9cc818bda21ce2d0e402cf3/kernel/src/main.rs#L83
--
jbowen
next prev parent reply other threads:[~2023-05-02 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 1:48 [TUHS] " Dan Cross
2023-05-02 1:55 ` [TUHS] " Clem Cole
2023-05-02 2:34 ` Larry McVoy
2023-05-02 3:05 ` Jason Bowen [this message]
2023-05-02 12:19 ` Dan Cross
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=C9773FDA-880A-48AB-8845-5CF8CC492C98@infinitecactus.com \
--to=jbowen@infinitecactus.com \
--cc=clemc@ccc.com \
--cc=lm@mcvoy.com \
--cc=tuhs@tuhs.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).