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

[mjmahon@aol.com (Michael J. Mahon)]

Matthew Montchalin wrote:

>Dave Althoff Jr wrote:
>|Matthew Montchalin (mmontcha@OregonVOS.net) wrote:
>|: Charlie wrote:
>|: |There is also a program called Sourceror.fp that is supposed to
>|: |print out a commented Applesoft listing (I have never tried it).
>|
>|: 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.)
>|
>|IIRC, Sourceror has all of the Applesoft, Monitor ROM, and DOS 3.3
>|standard labels in it.  I don't know about commented source from
>|Sourceror, but I think it's smart enough to know that $FDED is the entry
>|point for COUT and that $FD0C is RDKEY.....that alone is helpful...
>
>Yes, I think I would like that, being a newcomer to the Apple.
>And apparently since there isn't anything else cut out for the job.
>There must not be very much stuff written for the Apple, I guess.
>(Are you sure it won't let me use a predefined table of symbolic
>labels so I can disassemble software for non-Apple systems?)

Of course it permits labels to be equated in the disassembly
script--it is an excellent 6502 disassembler.

The particular case we are discussing--using Sourceror with
its "special script" on the reverse side of the disk to produce
a commented Applesoft disassembly--is _not_ its standard
mode of disassembly.  As was pointed out, when producing
the Applesoft disassembly, Sourceror is "decrypting" a manually
commented disassembly using the Applesoft ROMs as the
"key" to permit access.

The fact that these disassemblies are not cluttering the shelves
of every bookstore does not imply that "not very much stuff (was)
written for the Apple".  Quite the contrary!

-michael

Check out 8-bit Apple sound that will amaze you on my
Home page:  http://members.aol.com/MJMahon/