RiscOS or RISC OS?

I know, I know. World+Kitten knows that it is “RISC OS”.

But why?

Considering, in the Audio/DeviceFS discussion, a link was posted to https://www.riscosopen.org/viewer/view/castle/RiscOS/Sources/HWSupport/DualSerial/Docs/Attic/serial.htm?rev=1.1.2.1;content-type=text%2Fplain and you’ll notice that it says “RiscOS” in the source path. Now read the document, the second paragraph in the “1.0 Overview” section refers to “RiscOS”.

So if we are supposed to call it RISC OS, why does it look like Acorn called it RiscOS?

<ducks>

So if we are supposed to call it RISC OS, why does it look like Acorn called it RiscOS?

Bad boy. You know full well that there was a RiscOS out there on another processor. In those days people knew how to use a shift key and that spaces were significant so legal people knew that RISC OS was different to RiscOS.
By the time riscosopen came into being the use of a shift key was largely a lost art.

I know of “RISC/os” on MIPS, but that’s neither RISC OS nor RiscOS.
Google isn’t helping. It just gives loads of links to here. ;-)

Everybody English knows how to use the ⬆️ key¹, it’s how you get smilies. Frenchies, on the other hand, can type ‘em with one finger. That’s about the only positive point I can think of regarding AZERTY.

¹ It’s an up arrow, in case you are using a machine that can’t do this extended emoticon stuff, like 😷➕🈯️➕💊➡️🐮💨💩➡️💬 ²

² Roughly translated, face mask and finger (in throat) and medicine because the cow passed gas and did a huge smiling poo … there’s really nothing that can be said about that.

Perhaps we can call the next version “RiscOS 7”!

Side note: With semantic versioning, the next version should actually be a major number because it breaks backward compatibility (zero page). Since 6 is already taken, 7’s next in line! However, it won’t really “feel” like a major release. Perhaps we need to finish off Otter and bundle it with the OS, plus tweak a couple of things (maybe provide an option to swap Menu and Adjust for new users).

…Have I gone far enough off topic for this thread to be moved to Aldershot yet? :)

Perhaps we can call the next version “RiscOS 7”!

Side note: With semantic versioning, the next version should actually be a major number because it breaks backward compatibility (zero page). Since 6 is already taken, 7’s next in line!

Mr. Murray seems to have stirred up things.

Let’s just leave v7 alone for a while shall we? Not least because zero page doesn’t break anything that was using the official published API.

The fact that non-compliant items existed both in third party items and the core OS is just bad habits.

Surely RO7 is multi-processor?

Mr. Murray seems to have stirred up things.

Isn’t that what he’s here for?

And I guess you’re right about the documented API not changing…

Edit: Or not; the document says to use a minor version when the functionality becomes deprecated, but a major version once it’s actually gone.

Isn’t that what he’s here for?

:-P