Small C on the PC-Engine
HuC has a lot to be desired; it’s no secret. People that know how to get around its short comings, deal with it.
As much as I like assembler, I do like C. I’ve been wanting to code a small game for the PCE in C, for a while now. The past couple of days, I had a short conversation with Chilly Willy over at TE forums. CC65 to be exact. Looking over some of the stuff that you can do with it – it looks pretty decent, and most importantly – full manual page/bank control! That is a VERY important feature for optimization reasons alone. That was thee biggest gripe I had with HuC, over everything else that could be fixed with support code. Even some talk about how to optimize use for SuperGrafx extra ram with CC65.
I’m going to take a serious look at it this year. I don’t know if anyone else is interested in C for PCE, but I’ll be sure to make notes about my experiences. A lot of lib stuff can be ported over to CC65, from HuC. Since HuC is no longer being supported/worked on, I think it’s time to move over to CC65 for the PCE. At least there’s a muuuucchh bigger user base for CC65 (and not just for C64 either). The compiler supports 65C02 code, and to be honest (with C) 6280 isn’t really an improvement over it opcode wise. I doubt you’d see much of any improvement with the added instructions over 6280. They’re more convenient than anything else. And when they are faster, it’s for hand tuned assembly. Excluding the block transfer instructions. And supposedly CA65 supports 6280, so inline assembly should be fine.
SDCC looked decent as well, but there’s no support for 65x based processors (MCU version of 6800 was the closet thing). Too much work to add a new processor. CC65 it is.