Updated MACRO-10 blog post

jeffpar · Mar 21, 2017 · d59480b · d59480b
1 parent 3886147
commit d59480b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/_posts/2017-03-21-the-macro-10-assembler-50-years-later.md b/_posts/2017-03-21-the-macro-10-assembler-50-years-later.md
@@ -43,8 +43,8 @@ best.
 ### Introducing the MACRO-10 "Mini-Assembler"
 
 I decided that the shortest turn-around from *assembly* phase to *run* phase (aka *crash-and-burn* phase) would be to
-assemble the files in PDPjs itself.  So the PDPjs MACRO-10 "Mini-Assembler" was born.  Any machine that includes the PDPjs
-Debugger (like the machine below) now includes MACRO-10 support as well.
+assemble the files in PDPjs itself.  So the PDPjs [MACRO-10 "Mini-Assembler"](/modules/pdp10/lib/macro10.js) was born.
+Any machine that includes the PDPjs Debugger (like the machine below) now includes MACRO-10 support as well.
 
 {% include machine.html id="testka10" %}
 

diff --git a/modules/pdp10/lib/macro10.js b/modules/pdp10/lib/macro10.js
@@ -548,7 +548,7 @@ class Macro10 {
             this.parseText(macro.sText, macro.aParms, macro.aValues, macro.aDefaults);
             /*
              * WARNING: Our simplistic approach to macro expansion and processing means that recursive macros
-             * (such as the SHIFT macro contained in /apps/pdp10/tests/MACTEST1.MAC) could blow the stack.  Nothing
+             * (such as the SHIFT macro contained in /apps/pdp10/tests/macro10/TEXT.MAC) could blow the stack.  Nothing
              * bad should happen (other than a JavaScript stack limit exception aborting the assembly), but it begs
              * the question: did MACRO-10 perform any tail recursion optimizations or other tricks to prevent macros
              * from running amok?