<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
I think this is correctly patched:<br>
<br>
<br>
On 7/13/24 19:46, John Levine wrote:
<div class="moz-cite-prefix">
<div class="moz-text-plain" wrap="true"
style="font-family: -moz-fixed; font-size: 12px;"
lang="x-unicode">
<blockquote type="cite" style="color: #007cff;">
<blockquote type="cite" style="color: #007cff;">
<pre class="moz-quote-pre" wrap="">Aron Insinga <a class="moz-txt-link-rfc2396E" href="mailto:aki@insinga.com"><aki@insinga.com></a> said:
the DEC PDP-1 MACRO assembler manual says that a macro call
is expanded by copying the *sequence of 'storage words' and
advancing the current location (.) for each word copied*
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap=""></pre>
<blockquote type="cite" style="color: #007cff;">
<pre class="moz-quote-pre" wrap="">I am quite surprised.
</pre>
</blockquote>
</blockquote>
<pre class="moz-quote-pre" wrap="">I looked at the manual and I think he's misreading it. The "words" in
question are the tokens in the macro definition.
The example macros look pretty straightforward, instructions and
pseudo-ops that are expanded replacing dummy arguments by actual ones.
There's no conditional assembly so each macro is just a parameterized
chunk of code.
<a class="moz-txt-link-freetext"
href="https://bitsavers.org/pdf/dec/pdp1/PDP-1_Macro.pdf">https://bitsavers.org/pdf/dec/pdp1/PDP-1_Macro.pdf</a>
R's,
John
</pre>
</div>
</div>
</body>
</html>