Do I dare to go full CC65?

[GTR3QQ]

After watching ty SlithyMatt's 101 on 65c02 ASM, I have one conclusion
I'm going full highlevel.... for now for fast iterations and a general feel of the system, once possible, full ASM.

I also know there has been some latest advancements in rich coding 65c02 with optimized compiler.
And the fact it's running 8MegaHz!
So I'm kinda banking on this.

But I saw this https://www.xtof.info/coding-c-8-bit-6502-cpu.html.

…slide show is impossible to be acceptable.

I'll begin testing now, but I'd appreciate if you could share some insights on this matter,
is it worth it to bank on the raw power of x16 and good compiler or just eat the damn vegetables and stop wasting time on making static const so compiler will be much more happy....

[kelli217]

It’s SlithyMatt. A reference to the poem “Jabberwocky” contained within the work Through the Looking-Glass, the sequel to Alice’s Adventures in Wonderland.

’Twas brillig, and the slithy toves
Did gyre and gimble in the wabe;

[GTR3QQ]

It’s SlithyMatt. A reference to the poem “Jabberwocky” contained within the work Through the Looking-Glass, the sequel to Alice’s Adventures in Wonderland.

’Twas brillig, and the slithy toves
Did gyre and gimble in the wabe;

noted, sorry.

[Edmond D]

The WD 65C02 has shift instructions, but no slithy ones, so Shifty Matt works better

[ahenry3068]

It’s SlithyMatt. A reference to the poem “Jabberwocky” contained within the work Through the Looking-Glass, the sequel to Alice’s Adventures in Wonderland.

’Twas brillig, and the slithy toves
Did gyre and gimble in the wabe;

All mimsy were the borogoves,. And the mome raths outgrabe

[DragWx]

If you're already familiar with languages that look like C, then sure, give CC65 a try. The bonus is, you'll have CA65 right there if you want to try 6502 assembly.

I think writing C for 6502 is more of a convenience than anything else. C really helps when things get more and more complicated, like x86 or 68k architectures running more complex operating environments, less so when you're working with limited memory or limited clock speed environments like 6502 systems tend to be.

With the X16 running the 65c02 at 8 MHz, a C program will definitely run much better than it would on an Apple II, and I think access to some prewritten libraries (like CC65 provides) can be a nice boost for someone who wants to try writing something in C for it.

Also, don't be scared of assembly language. The 6502 is friendly enough to be a programmer's first entry into assembly programming, given its instruction set is pretty small and straightforward. The main thing you'd need to build up is your discipline with commenting/documenting what your code does, because its easy to lose track of what a routine is trying to do when you have to trace through several opcodes to figure it out. It's good to have that discipline anyway, but it's especially important with assembly programming.

[mortarm]

I have one conclusion I'm going full highlevel.... for now for fast irritations...

I don't think I'd want to use something that made me quickly irritated.

[ahenry3068]

I have one conclusion I'm going full highlevel.... for now for fast irritations...

I don't think I'd want to use something that made me quickly irritated.

Any kind of coding can be an exercise in irritation though can't it. The feeling of triumph is greater when you overcome the irritation

[DragWx]

I mentally autocorrected that to "fast iterations", because irritations are a given.

[ahenry3068]

I mentally autocorrected that to "fast iterations", because irritations are a given.

................. "DO OR DO NOT,.......... THERE IS NO TRY!"