@vfrmedia@kaniini Not anymore. They've been bought out by SoftBank, a Japanese firm; and, last I heard, they have close to 3000 employees now, as I recall. That's *plenty* of resources to invest in mid- to server-grade processors, all the while maintaining momentum in the embedded space. If they so desired.
So, I managed to convert both console output and keyboard input to COM interfaces on the Kestrel. However, with only 384 bytes of space for stack, plus RISC-V's boneheaded requirement that stacks remain 16-byte aligned for EVERY nesting level, this means I'm running out of stack just doing something simple like scrolling the screen.
Ouch.
Looks like I'm going to have to abandon COM and go back to using just a single entry-point vector for RAM-resident program linkage.
For the curious: http://github.com/tekktonic/onward , it's a forth and the pushed version isn't really there yet; it's pretty much just an rpn calculator. Locally I'm closer to working but still broken so I haven't pushed.
@carlchenet These issues, in part, are why I find Fossil to be so useful. I know it can never scale to projects that Git was made for, but the vast majority of projects I interact with daily don't need that kind of scalability anyway.
@evilscientistca I'm not color blind so far as any eye exams I've taken indicate. However, some people who look at this binary indicate "I see an orange star and a blue star," and when I look at it, I see one star that is very, very vaguely blue, but the other one looks white to me.
I think I'm just not very photo-sensitive in low light.
@clacke Yes; but the end result may or may not necessarily be that different. Chuck doesn't like parsing words, but he has created them in the past.
He even once implemented BASIC in Forth, and I don't think he bothered to use any parsing words to do it. It's in an old Forth Dimensions article, as I recall.