From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] g
Date: Thu, 12 Aug 2021 15:08:51 +0930 [thread overview]
Message-ID: <98DACA3D23BFCC10F9F6C6ACFA3248F2@musolino.id.au> (raw)
In-Reply-To: <CABB-WO9M7B0vx-ciRgH05q3aYgqFLtpgAw-z5RapaQdWXhAArg@mail.gmail.com>
> I wonder why file doesn't use Bprint. (As it is, it can call print
> any number of times before it prints a newline.)
If I had to guess: because it's easier to just type print(...) and not
have to setup a Biobuf for stdout.
> The case against is, of course, normal use of file just has a few
> files.
>
> The case against the case against is you were going to be linking in
> the bio stuff *anyway*. This has been true since First Edition.
I can't imagine there'd be much resistance if you were to provide a
patch.
next prev parent reply other threads:[~2021-08-12 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 18:03 Stuart Morrow
2021-08-11 1:13 ` ori
2021-08-11 20:15 ` Stuart Morrow
2021-08-11 20:32 ` Stuart Morrow
2021-08-12 5:38 ` Alex Musolino [this message]
2021-08-13 2:43 ` Alex Musolino
2021-08-14 21:38 ` Stuart Morrow
2021-08-14 21:45 ` Stuart Morrow
2021-08-15 2:42 ` Alex Musolino
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=98DACA3D23BFCC10F9F6C6ACFA3248F2@musolino.id.au \
--to=alex@musolino.id.au \
--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).