6502.org

You'll see it if you just click on the quote box at the bottom-right of the post frame.  The reply box will come up with what you're quoting, starting with, for example [quote="BigDumbDinosaur"] (but I had to put another pair of tags in there to keep the quote tag from doing its job).  You could edit it to say for example [quote="BDD"]

I always say, if it seems like shouting, just turn the font size down.  Personally, I like most programming to be in all cap.s.  The comments normally shouldn't be though, and I can understand if people don't like to keep finding themselves in the wrong case and always have to be hitting the cap.s-lock key off and on.  In prose however, the lines on the page exist because a book is more manageable than a long ribbon with a lump here and there for pictures.  But in programming, the separation into lines becomes very significant for visual factoring, and having ascenders and descenders (as lower-case does) blurs those divisions.  I especially dislike it when people mix lower-case a-f into them in hEx nUmBErS (since 0-9 are always capitals)!  Here on the forum where the non-[code] sections are in proportional spacing, when someone writes 3fff for example, in whatever font is used there, it initially looks like 3111 to me because the f's are so narrow:

Absolutely not the case for Fortran and Common Lisp, although COBOL and BASIC appear to have kept their all-caps spelling.

Got it! Thanks. I'd been using the little grey buttons inside the editor...

To come back on topic, I've just finished writing the interface for open() and close() - now to test them. Now I've got to grips (in assembler) with the parameter passing between everyone's different stacks it should be easier to get read() and write() done.

<shudder> Horses for courses, I guess; it was one of the first things I changed on a 6502 BASIC nearly fifty years ago. I hate code that shouts at me!

Neil

Again, JUST TURN THE FONT SIZE DOWN!  Capitalizing things to emphasize them or make them louder, although common, is incorrect.  That job should be left for bold or underlining.

Random fun-fact on CPUs emulating other CPUs: The new Raspberry Pico2 (RP2350 SoC) has both ARM and RISC-V cores, and the chip can boot from ARM or RISC-V. If it boots from RISC-V then firmware runs an ARM emulator so it can use the common ARM object code (to reduce the internal ROM capacity).

Do you have a handy link for the idea that the Pico 2 runs an ARM emulator? That's not an idea I've seen. (Of course, it could, and it can, but I've not seen anything official on those lines.) Edit: see below...

My understanding is that it has two ARM cores and two RISC cores, and two active slots each of which can be set, at reset time, to either flavour. The user's boot-time software is compiled for one or other flavour, and if the boot-time core detects that the image is for the other flavour it causes a boot into the other flavour. (Ref and also Ref)

Edit: ah, I see here this and later

If you'd like to dig deeper, the source code to the boot ROM is https://github.com/raspberrypi/pico-boo ... ree/master, and it uses the armulet emulator.

interesting! only 3k of ROM to emulate ARM on RISC-V:
https://github.com/raspberrypi/armulet? ... le#armulet