Re: How to detect EOFs in SEQ-files using M/C?

[Scott Hemphill <hemphill@hemphills.net>]

Matthew Montchalin <mmontcha@OregonVOS.net> writes:

> On 13 Sep 2002, Michael J. Mahon wrote:
> |>I doubt I could endure the nonsense that an 'automatic commenter'
> |>is likely to churn out.  (For instance, it probably says that a9
> |>means load accumulator with immediate, &c., sheeeesh, I already
> |>know that.)
> |
> |No, Sourceror uses a disassembly script for Applesoft which
> |produces a very fine commented disassembly.  It was a way to
> |make an Applesoft disassembly available only to those who had
> |Applesoft binary available already.
> 
> Meaning, I guess, that you can supply it with a ready-made table of
> symbol labels, and it will plug that in, and rely on it, when it
> disassembles?  But isn't that standard fare for a good source code
> generator?

No, what Sourceror really does is decrypt a hand-commented disassembly.
It uses the ROM BASIC as the key for the decryption.

Scott
-- 
Scott Hemphill	hemphill@alumni.caltech.edu
"This isn't flying.  This is falling, with style."  -- Buzz Lightyear