From: "Joseph Holsten" <firstname.lastname@example.org>
To: "Tautological Eunuch Horticultural Scythians" <email@example.com>
Subject: [TUHS] Re: interesting case of not getting the point: dc on a mac
Date: Sun, 22 Jan 2023 16:26:23 -0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
Supposedly https://cgit.freebsd.org/src/tree/contrib/bc is kept up to date, so I’d suspect the issue lies on the macOS side.
On Sun, Jan 22, 2023, at 16:20, ron minnich wrote:
> How do you write a dc that doesn't compile?
> The mind reels.
> On Sun, Jan 22, 2023, 7:16 PM Bakul Shah <email@example.com> wrote:
>> dc -V on MacOS shows 4.0.2. Repo link in the output of dc -V.
>> The current version is 6.2.2 but it doesn't compile on Ventura.
>> > On Jan 22, 2023, at 3:39 PM, ron minnich <firstname.lastname@example.org> wrote:
>> > dc
>> > >>>
>> > it prompts with '>>> '
>> > wonder where that came from? First time I've seen it.
>> > Seems to have a certain lack of understanding attached to it.
[-- Attachment #2: Type: text/html, Size: 1799 bytes --]
next prev parent reply other threads:[~2023-01-23 0:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 23:39 [TUHS] " ron minnich
2023-01-22 23:41 ` [TUHS] " ron minnich
2023-01-22 23:50 ` Warner Losh
2023-01-22 23:49 ` Steve Nickolas
2023-01-22 23:57 ` Joseph Holsten
2023-01-23 0:07 ` Steve Nickolas
2023-01-23 3:07 ` Dave Horsfall
2023-01-23 3:11 ` Larry McVoy
2023-01-23 13:43 ` Dan Cross
2023-01-23 13:59 ` ron minnich
2023-01-23 3:32 ` Steve Nickolas
2023-01-23 3:38 ` George Michaelson
2023-01-23 3:39 ` George Michaelson
2023-01-23 3:40 ` George Michaelson
2023-01-23 14:15 ` Dan Cross
2023-01-23 21:08 ` Joseph Holsten
2023-01-24 0:59 ` Adam Thornton
2023-01-23 0:15 ` Bakul Shah
2023-01-23 0:20 ` ron minnich
2023-01-23 0:23 ` George Michaelson
2023-01-23 0:26 ` Joseph Holsten [this message]
2023-01-23 0:39 ` Bakul Shah
2023-01-23 1:32 ` Rob Pike
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 NNTP newsgroup(s).