On Apr 12, 6:08=A0pm, Harry Potter  wrote:
> I want to create some software for the C64/128, Plus/4, Apple 2, NES
> and maybe the Vic-20, Apple 2gs and SNES, under Win32 and an running
> into problems. =A0I tried cc65, but it isn't exactly feature-rich. =A0I
> tried Aztec C, and the programs in the SAMPLES directory (for the C64,
> anyway) are *large* (>11k). =A0I have Quetzalcoatl, and it could
> probably produce small C64/Vic20 programs, but I haven't really tried
> it. =A0I want to create a cross-platform C compiler with the following
> features:
>
> * =A0 (Main feature) Support for hidden memory (i.e. $A000-$FEFF on a
> C64) and banked memory (C128/Apple 2 128k memory)
> * =A0 Support for longs and computer-specific float formats (both
> disablable, saving code)
> * =A0 Better optimizations
> * =A0 Better __fastcall and register declarations
> * =A0 Full zeropage support (direct pointer access and C variables in
> ZP)
> * =A0 Large programs separated into modules, each with its own main()
> function, called through a stub
> * =A0 The ability to replace a library module with another on the linker
> command line
> * =A0 Linker list files, rather than just on the command line
>
> and whatever else I can think of. =A0This program is giving me a hard
> time with debugging, as it's so complex. =A0Later, when I get the main
> tools working sufficiently, I'll ask for help. =A0Is this a good idea,
> or did somebody already beat me to itr?

Beat you to what? Some of what you are talking about are library
routines I think. The AUX memory stuff on the Apple II I already do...
and CC65 is doing something there too... what do you want to do
there???

How about the C64??? Harry what are you doing with overlays? OK and
did you look at the memory map that I am using with Aztec C?

I am creating holes where I want them and all that... I hardly think
the program code itself is large. Perhaps my load address, base
address, and what I am reserving for data is what you are reacting to.
How do you like what I am doing with the graphics compression and
such?

Quetezecoatl we all have too... it's not really C.

I think you need to step back and have a good look at the Aztec-C
compilers and then let's talk about how to get the source for them
released into the public domain and then make them ANSI compliant.

Of course that's my point of view so naturally I would say that:) And
I plan to do that too. If I can.

Glad you're having fun. You seem to have alot on your wish list...

Later,

Bill
--- SBBSecho 2.12-Win32