Huh. That's news to me; I haven't looked inside a computer since forever ago. I guess a 64-bit-wide ribbon cable would be a little awkward. But they still make circuit boards with one edge full of gold-plated tongues sticking out; do they hide a parallel-to-serial converter inside the sockets they plug into? I guess they could, these days, with super fast serial protocols.
Hell, it's not even a cable any more, I do still have a couple Serial ATA cabled drives in this, but the main drive in this is essentially a PCI-E thumb-drive at 1TB capacity. It's, kinda nuts, but it is still a gold plated tongue, just where you put it has changed.
I used to build things at a company that used ribbon cables, and I always adored when the "Red cable is pin one" was either faded or dotted or otherwise invisible... SO ANNOYING.
Still a child from my vantage point, then!
Yeah, I'm not that old, tbh. Numbers keep incrementing tho. Those darned numbers lol.
You mean you want to write a C++ compiler in Snap*!* ? That's not so very crazy. It'll be easier when we get around to text boxes. I wrote a (subset) Pascal compiler in Logo long ago (Computer Science Logo Style vol 3 ch 5: Programming Language Implementation). Someone wrote, astonishingly, a Scheme interpreter in Scratch! No custom blocks! No abstraction! The author then disappeared off the face of the earth. That was their one and only project.
Huh, that's a shame. That sounds cool.
When I discovered Snap in December 2017, the first three textbooks I devoured were your LOGO books. I then jumped onto SICP and Scheme. So I've messed around with text languages and I understand logo and scheme far better than I ever did C or C++, but ask me to program something in them? Good Luck. I can follow examples really well, but sit me infront of an interpreter and ask me to solve a problem. Knowledge flies through nearest window
That would be GP. Although yes I saw that you want to write your own.
I mean... if someone's beat me to it, I'd take it, but it all boils down to me wanting to know how the sausage is made. I don't really NEED to know that, but I do. I'll look into that.
Speaking as someone who is sometimes asked such questions, I diffidently suggest that if you want a detailed answer you have to ask a detailed question. If you can articulate what you really want to know, people will be happy to talk about their work, imho.
Questions like, for example;
Why the flying Duck are we still on 64bit, where is 128 or 256bit?
Why are we still pretending RISC is anything other than garbage?
Endianess? Nobody Cares, can we leave binary in the bin please?
You know, questions that are easy to answer and don't provoke arguments that just starting will take half an hour just to explain the basics of the basics.
I have issues with the path technology is taking. I'm the first to disclaim my opinions as crack pot nonsense, but only really because I can't prove/disprove them. As I said, Slightly Crazy. (Utterly Insane)