From: George Michaelson <ggm@algebras.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: interesting case of not getting the point: dc on a mac
Date: Mon, 23 Jan 2023 13:38:52 +1000 [thread overview]
Message-ID: <CAKr6gn0=Mc5gcqwExzv8NpCpZqcXCni9MhbVVey=EmjBQRSWJw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2301222230010.31399@sd-119843.dedibox.fr>
ggm@GGM-802602 ~ % uname && dc --version |egrep git\|dc
Darwin
dc 4.0.2
Report bugs at: https://git.yzena.com/gavin/bc
ggm@GGM-802602 ~ %
finley% uname && dc --version |egrep git\|dc
FreeBSD
dc 5.2.2
Report bugs at: https://git.yzena.com/gavin/bc
finley%
On Mon, Jan 23, 2023 at 1:33 PM Steve Nickolas <usotsuki@buric.co> wrote:
>
> On Mon, 23 Jan 2023, Dave Horsfall wrote:
>
> > On Sun, 22 Jan 2023, Steve Nickolas wrote:
> >
> >> I think there was one particular dc clone...guy whose name started with
> >> a G? and his version did that.
> >
> > On my ancient MacBook Pro (13-inch, mid 2010, High Sierra 10.13.6):
> >
> > mackie:~ dave$ dc
> > (^D)
> > mackie:~ dave$ dc -V
> > dc (GNU bc 1.06) 1.3
> >
> > On my ancient FreeBSD server:
> >
> > aneurin% dc
> > (^D)
> > aneurin% dc -V
> > dc (BSD bc) 1.3-FreeBSD
> >
> > Nil prompt in both cases.
> >
> >> Most Linux versions use GNU's which Does The Right Thing®™©.
> >
> > Perhaps so, but I try to avoid using Penguin/OS and GNU... I don't like
> > its licence conditions ("free" it ain't), and I would rather write my own
> > libraries than be constrained by Stallman's conditions.
> >
> > -- Dave
>
> I've dealt with fanboys telling me how to do GPL on my own stuff, and it
> left a sore taste in my mouth. I don't care about the stuff I *use*, but
> it did leave me very negative about the GPL itself, and if it seems that
> some of the OS-building stuff I've been talking about here and elsewhere
> has anything to do with a grudge against GNU,...well...it does.
>
> Still, GNU does seem to have more respect for precedent than a lot of
> johnny-come-lately coders trying to reimplement stuff themselves.
>
> -uso.
next prev parent reply other threads:[~2023-01-23 3:40 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 [this message]
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
2023-01-23 0:39 ` Bakul Shah
2023-01-23 1:32 ` Rob Pike
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='CAKr6gn0=Mc5gcqwExzv8NpCpZqcXCni9MhbVVey=EmjBQRSWJw@mail.gmail.com' \
--to=ggm@algebras.org \
--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).