home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.atari.8bit
- Path: sparky!uunet!gatech!destroyer!news.iastate.edu!pv0a27.vincent.iastate.edu!tgreen
- From: tgreen@iastate.edu (Todd Greenfield)
- Subject: patched as6502 on archive (was Re: Kermit-65 source code)
- Message-ID: <tgreen.726785150@pv0a27.vincent.iastate.edu>
- Sender: news@news.iastate.edu (USENET News System)
- Organization: Iowa State University, Ames IA
- References: <92358.112139JJMCWILL@MTUS5.BITNET> <BzyKMB.CMJ@merk.com> <72769@cup.portal.com> <C07sBJ.Juv@merk.com> <1993Jan03.003650.10553@uunet!scarrow>
- Date: Mon, 11 Jan 1993 20:45:50 GMT
- Lines: 31
-
-
- >In article <C07sBJ.Juv@merk.com> winston@merk.com (Winston Smith) writes:
-
- >> "Just when you thought it was safe to go back in the water...."
- >>
- >> Well, the KERMIT-65 saga continues. I was able to locate a 6502
- >> cross-assembler written in C. It is able to generate an ASCII text
- >> assembler listing, both with program source, or just with assembled byte
- >> values given in ASCII text. This program is able to run on a "Kernighan
- >> and Ritchie" C compiler. Unfortunately, the program that accompanies the
- >> assembler, that is supposed to turn the text characters into binary
- >> code, is written in ANSI C, and the file calls make the K&R C compiler I
- >> am using do strange things. <* ARG! *> Why can't this assembler generate
- >> UUENCODE output as an option? Why do people --DO-- things like this? Why
- >> do they add non-compatible ANSI C programs to programs that are K&R C
- >> compliant? This is driving me crazy!
-
-
- well, I decided to fix as6502 to output the object file
- in atari format. I just put it up on the archive,
- in 8bit\New\as6502_atari.tar.Z (use uncompress then tar xf
- on unix to unarchive). I included a msdos exe.
-
- I'm thinking about hacking it a bit more - to make it more
- like MAC65 - would there be any interest in this? Probably
- won't have time though.
-
- todd
- --
- Todd Greenfield
- tgreen@iastate.edu
-