Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!udel!haven!ni.umd.edu!ni.umd.edu!zben
From: zben@ni.umd.edu (Ben Cranston)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Know What You Are Doing
Summary: Some of us still use fanfold paper
Message-ID: <1991Apr1.225353.4397@ni.umd.edu>
Date: 1 Apr 91 22:53:53 GMT
References: <49900005@primerd> <1991Apr1.190102.12345@eplrx7.uucp>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland at College Park
Lines: 60
Nntp-Posting-Host: ni.umd.edu

In article <1991Apr1.190102.12345@eplrx7.uucp> leipold@eplrx7.uucp
(Walt Leipold) writes:

> You know the (only) thing I miss from the ol' mainframe days?  Fan-fold
> printer paper!  I never got disoriented at a page boundary, the stuff was
> 132 columns wide so there was plenty of room for doodling alternate
> algorithms, the print was big (by modern standards), and if I got *really*
> confused, I found a long hallway, unrolled the entire source file, and
> crawled back and forth until I understood what was going on.  

When I want a listing of one of my assembly language programs:

1. My makefiles have "asm -L" statements, so a whatever.a.lst file gets made.

2. My makefiles have a "listing" target, like this:

listing	D
	catlist netprint.r dinstall.a.lst netprint.a.lst setup.a.lst 6
	>harddisk:onsiteprint

(You have to close your eyes and imagine that the "D" is a long script F
and the 6 is a greek "del" character :-)

So a "make listing" makes a file called "onsiteprint" containing the source
of the resource file and the assembly language listing.  The catlist proc
looks like this:

# catlist <files>
If 0!={#}
 For name in {"Parameters"}
  echo 6f
  catenate {name}
 End
Else
 For name in E
  If ("{name}" =~ /E.p/) || ("{name}" =~ /E.c/) || ("{name}" =~ /E.a.lst/)
   echo 6f
   catenate {name}
  End
 End
End

(Yeah, close your eyes and see the E as a double wavy equals sign...)

3. I run a mdqs qpr program on "onsiteprint" and send it to a unix machine
via TCP/IP.  If I ever get a spare minute I will write a MPW tool that does
the catenation, the form feed between files, and the network send.  This
would compress steps 2 and 3 together.

4. The unix machine spools the printer files.  The queue I spool to specifies
routing to a Univac 1100 mainframe.

5. Software on the Univac 1100 receives the unix-format print file and
converts it to Univac internal format, then to IBM print file format.

6. The IBM formatted file is sent via a HASP link to an IBM 3090 machine
which feeds it to an IBM 3800 laser printer which prints nice listings on
(ta da!) fanfold computer paper.  Lots of width for dem assembly listings
and lots of header and trailer pages to play tic-tac-toe on while waiting
for all this stuff to happen...