The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <>
Subject: [TUHS] Re: ed: f command (facts vs. file)
Date: Fri, 22 Jul 2022 13:14:33 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> What's the background for the comment about ``facts''?
(for DMR's QED for GE-TSS on the GE 635):

    _History of QED_
    The original QED was implemented at the University of
    California, Berkeley [4]. Substantially redesigned versions
    were written by the second author (KLT) for the CTSS system
    at MIT [1] and in BCPL for MULTICS. The latter version has
    also been available under GE-TSS using I/O routines supplied
    by A. W. Winikoff.

    _This version of QED_
    The present incarnation of QED was implemented in GMAP by
    the first author (DMR). It offers noticeable improvements
    in speed, program size, and text packing density over the
    BCPL version, of which it is a direct descendant. New
    facilities include a redesigned Global command and a
    numerical capability

The F(acts) command appears on page 9 (pdf page 10)

    The F command causes QED to type out
    1) the number of words on QED's "free list",
    2) the highest memory location used for text storage, and
    3) the current core allocation.

    When the third number gets near 32K, take care not to exceed the core

  reply	other threads:[~2022-07-22 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 17:30 [TUHS] Re: ed: multiple addresses (with semicolons) Douglas McIlroy
2022-07-18 10:52 ` markus schnalke
2022-07-22 16:17   ` [TUHS] Re: ed: f command (facts vs. file) markus schnalke
2022-07-22 17:14     ` Phil Budne [this message]
2022-07-23  5:47       ` markus schnalke

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:

* 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).