The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] The birth of the Z3
Date: Sun, 13 May 2018 17:30:42 -0400 (EDT)	[thread overview]
Message-ID: <20180513213042.0914C18C09C@mercury.lcs.mit.edu> (raw)

    > From: Clem Cole

    > Their is a open question about the need to support self modifying code
    > too. I personally don't think of that as important as the need for
    > conditional instructions which I do think need to be there before you
    > can really call it a computer. 

Here's one way to look at it: with conditional branching, one can always
write a program to _emulate_ a machine with self-modifying code (if that's
what floats your boat, computing-wise) - because that's exactly what older,
simple microcoded machines (which don't, of course, have self-modifying code
- their programs are in ROM) do.

	Noel


             reply	other threads:[~2018-05-13 21:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 21:30 Noel Chiappa [this message]
2018-05-13 21:44 ` Mike Markowski
2018-05-14  3:27   ` Dave Horsfall
  -- strict thread matches above, loose matches on Subject: below --
2018-05-11 22:21 Dave Horsfall
2018-05-12 15:04 ` Clem Cole
2018-05-13  6:52   ` Greg 'groggy' Lehey
2018-05-13 21:07     ` Clem cole

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=20180513213042.0914C18C09C@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).