Yes. For 8 bit Apples there is HyperC, Aztec C and Small C. The first 2
are easily found on the web. The last one is from The Byteworks and
should be available in it's 8 bit assembler version Orca/M which (I
think) you can get from Syndicomm. HyperC and Aztec C are not ANSI C
compliant but are well developed for the 8 bit Apple II. The legalities
of these systems are dubious but HyperC is considered legal as abandoned
shareware.
An alternate method would be the cross development system CC65. A well
developed, mostly ANSI C compiler.
As an aside, the GS has a robust development environment. Well,
technically 2. The Byteworks developer tools and the APW tools which
were based on them.
Cheers,
Mike T.
Do you have a Mac? I used MPW for the GS. I'm sure I have a copy.
-- Charlie Springer
regards,
Andrew
No, I have a II +
>
>-- Charlie Springer
Would compiling small jobs on an Apple 2 be about as 1/3 as fast as an
original PC?
That would be totally dependent on the efficiency of the compiler.
-michael
NadaNet file server for Apple II computers!
Home page: http://members.aol.com/MJMahon/
"The wastebasket is our most important design
tool--and it's seriously underused."
> John wrote:
>
>> Would compiling small jobs on an Apple 2 be about as 1/3 as fast as an
>> original PC?
>
> That would be totally dependent on the efficiency of the compiler.
>
> -michael
Turbo Pascal (ver 1, 2 or 3) for CP/M-80 running on an Apple II+ with
a 6 MHz Z80 AppliCard complied approximately as quickly as the same
version of Turbo Pascal for MS-DOS running on a 4.77 MHZ 8088 PC.
Frankly, I don't remember which one of the two was fastest, but the
difference wasn't big.
An interpreted Applesoft program ran about half as fast on the 1 MHz
6502 compared to if the same program ran interpreted in MBASIC on
CP/M80 on a 6 MHZ Z80 AppliCard on the same Apple II.
--
----------------------------------------------------------------
Paul Schlyter, Grev Turegatan 40, SE-114 38 Stockholm, SWEDEN
e-mail: pausch at stockholm dot bostream dot se
WWW: http://stjarnhimlen.se/
Small-C is a subset of the full language. Specific differences will
be
discussed later. For someone writing production code, Small-C will be
a
risky choice. Small-C is primarily intended to fill three needs:
1. Small-C shows how to install a compiler in the ORCA/M
environment, and thus serves as an example to compiler writers who
would
like to bring a compiler up on ORCA/M.
2. Small-C comes with source code, and is written in itself. This
makes it a valuable tool for anyone who would like to learn more
about
compilers, or who needs to implement a special purpose language.
3. Small-C, while not a full implementation, will be useful to those
needing a compiler until full languages are available on ORCA/M.
If you fall into one of those categories, then Small-C is for you. If
you do
not, another compiler would probably be a better choice.
-=>JB<=-
> 3. Small-C, while not a full implementation, will be useful to those
> needing a compiler until full languages are available on ORCA/M.
....and when will *that* happen? ;-)
And what does "full language" mean here? K&R-C as it existed in the
heydays of the Apple II? Or C-89? Or perhaps even C-99?
(from Answers.com )
----- snip snip -------------------------------
Small-C
In computing, Small-C is both a subset of the C programming language,
suitable for resource-limited microcomputers and embedded systems, and
an implementation of that subset. Originally valuable as an early
compiler for microcomputer systems available during the late 1970s and
early 1980s, the implementation has also been useful as an example
simple enough for teaching purposes.
The original compiler, written in Small-C for the Intel 8080 by Ron
Cain, appeared in the May 1980 issue of Dr. Dobb's Journal. James E.
Hendrix improved and extended the original compiler, and wrote The
Small-C Handbook. According to his own recollection, he developed
Small-C partially on a Unix system to which he had access. Small-C was
important for tiny computers in a manner somewhat analogous to the
importance of GCC for larger computers. Just like its Unix
counterparts, the compiler generates assembler code, which then must
be translated to machine code by an available assembler.
---- end of snip -----------
There is more in the article about why people found it interesting.
Well I know all that already -- I also have Henrix book.
But it didn't answer my question. I didn't ask about Small-C - instead
I asked a question about that future "full languages available on ORCA/M".
But I suppose it never materialized and never will....