/templeos/ - The 64-Bit Temple Operating System

My wisest tip is to use the switch() statement. Many people think a switch() statement is identical to if-else-if-else…

My other wisest tip is that naming of functions and variable is one of the most important skills.

>>1149

When it comes to naming things, at some point you will invent something brand-new. At that point, you should invent a brand new name because it no longer qualifies as the same sort of item that already exists.

I called my filesystem "Native" for a long time, then picked an off-the-wall name, "RedSea". Marketing is a fascinating field. Don't under-rate what marketeers do when they pick names that work in many countries. I named my C-language "C+" at first and finally came-up with "HolyC".

http://www.templeos.org/Wb/Doc/HolyC.html

HolyC is not very modern. You will use one language at work that is nasty and modern; at play, you can use HolyC and dodge the nagging-preaching computer people.

>>1150

By modern, I mean with lots of compile-time checking… rigid type checking with "const" and all that.

In theory, type checking prevents bugs early. I find it an annoying pain in the ass.

There is no cruft in HolyC.

Integers are U0,I0,I8,U8,I16,U16,I32,U32,I64,U64.

You don't need to do big constants with a "l".

> long long i=12345678901234l;

PrintF() does not need the "%ld", just "%d".