Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 (Tek) 9/26/83; site tekecs.UUCP
Path: utzoo!watmath!clyde!akgua!sdcsvax!sdcrdcf!hplabs!tektronix!orca!tekecs!joemu
From: joemu@tekecs.UUCP (Joe Mueller)
Newsgroups: net.micro.cbm
Subject: Re: compilers for the 6502
Message-ID: <3806@tekecs.UUCP>
Date: Fri, 25-May-84 15:00:58 EDT
Article-I.D.: tekecs.3806
Posted: Fri May 25 15:00:58 1984
Date-Received: Fri, 1-Jun-84 04:58:31 EDT
References: <12900002@acf4.UUCP>
Organization: Tektronix, Wilsonville OR
Lines: 18

About the only way to handle automatics are to set up your own stack
(the 6502's is a cruel joke) and allocate them from the pseudo-stack.
I have been in the process of building a C-64 c compiler for about
8 months now. It is in pretty good shape but will not be available
until I get the  rest of the support programs ready (linker, assembler,
loader, librarian). I wasn't going to say anything about it until it
was ready, but seeing all this discussion prompted this response.

If everyone is in such dire need for a compiler (I agree what's
available is either too expensive or worthless), would there be
suffecient interrest in an incremental release? I may be able to
provide something within a couple months and provide updates real
cheap. Also what would be the minimum functionality for initial
release? Currently I don't have structures, unions, parameter
substitution in macros, multidimentional arrays, bit fields and floating
point. I could also drop separate compilation & relocatability.

Questions/comments are welcome.