dillon@CORY.BERKELEY.EDU.UUCP (02/07/87)
Lets say you want to look at a hunk disassembly of AMIGA.LIB . The ascii dump that HUNKS gives for that is well over 200K. Assuming you have limited memory and can't have the file in RAM and edit it at the same time, and assuming you don't want to wait for it to dump to disk: CLI 1> hunks >pipe:xx amiga.lib CLI 2> med pipe:xx where HUNKS is the hunk-dumping program, and MED is an editor. MED was barely able to fit the entire file in my 512K Amiga. Another cute thing I did just for laughs was to Capture to a pipe:xx file from my terminal program, and have a CLI 1> wordcount pipe:xx running from the CLI. When I finish the session and the terminal program closes the Capture, the wordcount gets an EOI and tells me how many chars/words/lines came over the modem in that session. Any program which writes out small buffer sizes to disk can be made more efficient by specifying a pipe as the output file, and then running a copy concurrently (which uses large buffer sizes): CLI 1> hunks >pipe:a amiga.lib CLI 2> fgrep >pipe:b LVO pipe:a CLI 3> copy pipe:b file I haven't tried this yet, but it should be possible to specify a pipe as a compiler's temporary file, then have all passes of the compiler, including the assembler or code generator in memory and running at the same time. Needless to say this presumes having a lot of memory in your Amiga... say, 2 Megs? -Matt