From: George Michaelson <ggm@algebras.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] PL/I stuff - was: Book Recommendation
Date: Sat, 27 Nov 2021 10:01:13 +1000 [thread overview]
Message-ID: <CAKr6gn2GeJEwcZYLeU6NERrL26D8SbbF4Xie8=20q0QKHL6ZZA@mail.gmail.com> (raw)
In-Reply-To: <CAD2gp_SY+h88i=zduugJCMS1Bpc7UO6jAUQur9mqTqzg0p-WuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1821 bytes --]
I've always felt a huge disconnect between the decus tape philosophy of
code, and the IBM approach of "this software feature costs you more" about
things like language extensions and -O(n) flags (to use modern c compiler
mental models)
I did find the hardware trick of detuning the clock to sell more boxes and
charging to remove the resistors also a bit iffy but I kind of understood
it. But, being asked by some major client (defence) to implement recursion
support and then charging everyone feels like the business model designed
to kick start people cutting their own code to stop depending in yours -and
I believe this is somewhat the story of university multi access systems on
IBM and these seven dwarf competitors. Burroughs by comparison had (I am
told, I didn't use them) shit hot code, the kernel was in a ci/cd
deployment framework with smarts. And DEC had the decus tapes and
everything in VMS was on microfiche.
On Sat, 27 Nov 2021, 7:24 am John Cowan, <cowan@ccil.org> wrote:
>
>
> On Fri, Nov 26, 2021 at 3:32 PM Tom Ivar Helbekkmo via TUHS <
> tuhs@minnie.tuhs.org> wrote:
>
> Is there any relationship, other than pure coincidence, between this
>> naming scheme and DEC's F, G, and H floating point number formats?
>>
>
> I don't think so. The System/360 letters referred specifically to the
> amount of memory available, so a D compiler would run on a D machine with
> 256K, and E/F/G were 512K/1M/2M.
>
> The DEC floats were an extension of Fortran's exponent letters: D=double,
> E=generic, F=single. G is a variant of F with a different
> mantissa/exponent balance, and H is double double. S and T floats came
> later and were bit-for-bit compatible with IEEE binary32 and binary64
> formats. Lisp went a different way: to D, E, F they added S for small
> floats and L for large floats.
>
[-- Attachment #2: Type: text/html, Size: 2925 bytes --]
next prev parent reply other threads:[~2021-11-27 0:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 23:54 Douglas McIlroy
2021-11-25 16:35 ` Paul Winalski
2021-11-25 18:15 ` Steve Nickolas
2021-11-26 16:59 ` Paul Winalski
2021-11-26 20:30 ` Tom Ivar Helbekkmo via TUHS
2021-11-26 21:22 ` John Cowan
2021-11-27 0:01 ` George Michaelson [this message]
2021-11-27 16:12 ` Paul Winalski
-- strict thread matches above, loose matches on Subject: below --
2021-11-27 15:25 Noel Chiappa
2021-11-27 15:53 ` Charles H Sauer
2021-11-16 14:57 [TUHS] " Douglas McIlroy
2021-11-23 2:28 ` Mary Ann Horton
2021-11-23 21:54 ` Thomas Paulsen
2021-11-24 15:18 ` Richard Salz
2021-11-24 22:19 ` Charles Anthony
2021-11-24 22:29 ` [TUHS] PL/I stuff - was: " Will Senn
2021-11-24 23:00 ` Rob Pike
2021-11-24 23:13 ` Richard Salz
2021-11-25 1:48 ` Nelson H. F. Beebe
2021-11-25 2:03 ` George Michaelson
2021-11-25 14:47 ` Clem Cole
2021-11-26 22:20 ` Alan Glasser
2021-11-26 22:33 ` Alan Glasser
2021-11-27 0:23 ` Dennis Boone
2021-11-27 0:30 ` Larry McVoy
2021-11-27 0:47 ` Charles H. Sauer
2021-11-27 2:43 ` Alan Glasser
2021-11-27 0:56 ` Warner Losh
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='CAKr6gn2GeJEwcZYLeU6NERrL26D8SbbF4Xie8=20q0QKHL6ZZA@mail.gmail.com' \
--to=ggm@algebras.org \
--cc=tuhs@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).