From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] The most surprising Unix programs
Date: Fri, 20 Mar 2020 13:47:44 -0600 [thread overview]
Message-ID: <a33b102b-b26a-1f11-f516-80d9d0fa05ef@tnetconsulting.net> (raw)
In-Reply-To: <fc23c61e-81e5-3f5a-adf4-28c8fd35fb0f@tnetconsulting.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On 3/20/20 1:43 PM, Grant Taylor via COFF wrote:
> What I think I'm hearing you say is that with RPN you were shouldering
> part of the computational load based on how you were entering things so
> that they aligned as necessary with the stack. Conversely, you were
> simply "plug and chug" (as I've heard elsewhere). Meaning you entered
> the equation / formula and were largely hands off from the calculation.
I can see how this could be translated to RPN could cause someone to
feel like they have a better understanding of what's being calculated.
Conversely, infix notation leaving someone feeling separated from the
calculation and having much less of an understanding of what's being
calculated.
This separation making it more likely that people will have problems
estimating and having any idea if what they're doing makes any sense or not.
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200320/13026aab/attachment.bin>
next prev parent reply other threads:[~2020-03-20 19:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202003132331.02DNVaxN061501@tahoe.cs.Dartmouth.EDU>
[not found] ` <7ec47fd97b1a3d383ffed428f21f5287@firemail.cc>
[not found] ` <CALMnNGjuQybT8_g_g498dOuV9OV67JEOn7Mz34vG1TeO9WrkYw@mail.gmail.com>
[not found] ` <cdef128a21d3ed60c79dc5253d761652@firemail.cc>
[not found] ` <20200317145723.GF26660@mcvoy.com>
2020-03-17 15:41 ` [COFF] [TUHS] " clemc
2020-03-17 22:48 ` dave
[not found] ` <alpine.BSF.2.21.9999.2003180908300.10777@aneurin.horsfall.org>
[not found] ` <c44be69f-846d-55f2-2709-8765f7f5fcc4@gmail.com>
2020-03-19 21:31 ` dave
2020-03-19 21:30 ` cym224
2020-03-19 21:48 ` stewart
2020-03-21 2:49 ` dave
2020-03-21 2:55 ` lm
2020-03-21 4:01 ` [COFF] HP calculator emulators (was: The most surprising Unix programs) grog
2020-03-21 7:21 ` [COFF] The most surprising Unix programs tih
2020-03-21 21:10 ` mparson
[not found] ` <6D9CA6C2-BDF2-4BCA-9503-0F8415C594C9@guertin.net>
2020-03-20 15:40 ` [COFF] [TUHS] " gtaylor
[not found] ` <202003201640.02KGerlG470796@darkstar.fourwinds.com>
[not found] ` <0b0d0ba3-7eae-a844-cc9a-ae542edb302b@tnetconsulting.net>
2020-03-20 19:11 ` clemc
2020-03-20 19:31 ` [COFF] " tih
2020-03-20 19:43 ` gtaylor
2020-03-20 19:47 ` gtaylor [this message]
2020-03-20 20:10 ` terry
2020-03-20 20:37 ` clemc
2020-03-20 20:30 ` tih
2020-03-20 20:31 ` clemc
2020-03-20 22:51 ` dave
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=a33b102b-b26a-1f11-f516-80d9d0fa05ef@tnetconsulting.net \
--to=coff@minnie.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).