Fix up notes to use interp-stdin.

Author: dvanhorn

www/notes/abscond.scrbl

@@ -185,9 +185,9 @@ produces it's meaning:
 )
 
 We can add a command line wrapper program for interpreting Abscond
-programs saved in files:
+programs from stdin:
 
-@codeblock-include["abscond/interp-file.rkt"]
+@codeblock-include["abscond/interp-stdin.rkt"]
 
 The details here aren't important (and you won't be asked to write
 this kind of code), but this program @racket[read]s the contents of a
@@ -196,7 +196,7 @@ well-formed Abscond program, then it runs the intepreter and displays
 the result.
 
 For example, interpreting the program @tt{42.rkt} shown above:
-@shellbox["racket -t interp-file.rkt -m 42.rkt"]
+@shellbox["cat 42.rkt | racket -t interp-stdin.rkt -m"]
 
 Even though the semantics is obvious, we can provide a formal
 definition of Abscond using @bold{operational semantics}.
@@ -475,7 +475,7 @@ adds up to much more efficient programs.  Just to demonstrate, here's
 a single data point measuring the difference between interpreting and
 compiling Abscond programs:
 
-@shellbox["time -p racket -t interp-file.rkt -m 42.rkt"]
+@shellbox["cat 42.rkt | time -p racket -t interp-stdin.rkt -m"]
 
 Compiling:
 

www/notes/iniquity.scrbl

@@ -113,9 +113,9 @@ is updated to include function applications.
 
 Because of the change from a program being a single expression to a
 sequence, we have to update the utilities that read program files,
-i.e. @tt{interp-file.rkt} and @tt{compile-stdin.rkt}:
+i.e. @tt{interp-stdin.rkt} and @tt{compile-stdin.rkt}:
 
-@codeblock-include["iniquity/interp-file.rkt"]
+@codeblock-include["iniquity/interp-stdin.rkt"]
 @codeblock-include["iniquity/compile-stdin.rkt"]
 
 
@@ -197,7 +197,7 @@ and @racket[odd?]:
 
 And the utility for interpreting programs in files works as well:
 
-@shellbox["racket -t interp-file.rkt -m example/len.rkt"]
+@shellbox["cat example/len.rkt | racket -t interp-stdin.rkt -m"]
 
 
 @section[#:tag-prefix "iniquity"]{Conventions of Calling}