From: "John Levine" <johnl@taugh.com>
To: coff@tuhs.org
Subject: [COFF] Re: ancient macros, machine code translation,as mental architecture models
Date: 14 Jul 2024 18:02:35 -0000 [thread overview]
Message-ID: <v713rr$1foh$1@gal.iecc.com> (raw)
In-Reply-To: <20240713234644.AAD0B8F88DE4@ary.qy> <CAKH6PiUj=ndZuGUoCxpR=ekZ-suchE5ofLa+6pWyE-AhcAO8vw@mail.gmail.com> <6a0f5b10-a2df-4117-b0ea-71802b6a7c26@insinga.com>
According to Aron Insinga <aki@insinga.com>:
>On 7/13/24 19:46, John Levine wrote:
>> I looked at the manual and I think he's misreading it. The "words" in
>> question are the tokens in the macro definition. ...
>Possibly, but they use 'syllables' for tokens (symbols or integers), and
>they say here that they advance the location counter after each word
>copied. If they were copying characters into the input stream, they
>would not be incrementing the location counter ('.') after each word
>transferred.
If you really want to know what it did, here's the internals manual.
The description of the macro facility starts on page 19 and it is
quite clear that they're storing a tokenized version of the macros, so
they're not copying characters, but they're not just copying assembled
instructions either.
https://bitsavers.org/pdf/dec/pdp1/F36P_PDP1_Macro_Internals.pdf
The macro instruction facility in MACRO is both the strongest and weakest part of the program.
It is the strongest in the sense that it is thot part of the program which contributes most toward
ease of programming, especially in setting up tables of specialized format. It is the weakest
in that it is quite inflexible and does not incorporate any of the more significant improvements
in assembler technology that have occurred since the logic was first written in 1957.
--
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
next prev parent reply other threads:[~2024-07-14 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 22:00 [COFF] " Douglas McIlroy
2024-07-13 23:46 ` John Levine
2024-07-14 0:54 ` Dan Cross
2024-07-14 1:04 ` Aron Insinga
2024-07-14 0:56 ` Aron Insinga
2024-07-14 18:02 ` John Levine [this message]
2024-07-15 1:44 ` [COFF] Re: ancient macros, " Aron Insinga
2024-07-15 14:09 ` Paul Winalski
2024-07-15 12:37 Douglas McIlroy
2024-07-15 14:26 ` Paul Winalski
2024-07-15 14:38 ` Bakul Shah via COFF
2024-07-15 19:39 ` John Levine
2024-07-16 19:55 ` Aron Insinga
2024-07-16 20:09 ` Aron Insinga
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='v713rr$1foh$1@gal.iecc.com' \
--to=johnl@taugh.com \
--cc=coff@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).