461–466 of 466 posts
Earlier quoted context omitted.
I do most of my programming in a binary world.
You do none. You program FOR the binary world, but in a complex 3D reality
Jokes aside though, I doubt that no programmers are immersed in the computer while they code. It totally is a different world, just implemented inside this one.
Earlier quoted context omitted.
I"m even not agreeing with the const part. The standard did define const API"s, so why shouldn"t we follow? I know that C const are only half of C++ consts, but still. Still catching const errors somewhere because I do use const in APIs. I only agree with "Declare all functions static except for entry points". s8(s) is only for literal strings, it should be called s8_c instead and keep s8 for the default ctor. The st…
Can you explain the static functions thing? What’s the benefit of declaring all functions static if you’re compiling them as a single translation unit anyway?
Earlier quoted context omitted.
Computer architecture is optimized for 32+ bit aligned access to most things. The gain is (usually, but not always!) performance.
I'm afraid you are only slightly correct. Architectures are generally optimized for aligned access (or disallow unaligned access), but what counts as "aligned" is different for each type. A char type that is used for a bool can be accessed on any byte boundary because the alignment of a char is 1. The alignment of a 32-bit value is 4. However, architectures are generally more optimized for 32-bit operations in regist…
Earlier quoted context omitted.
Not sure about 64-bit `int`, but it is 16-bit on some 16-bit micros, such as the AVR line (used by the original Arduino).
Ti dsps have 48bits for long.
This is my personal style: http://edit.rupy.se/?host=move.rupy.se&path=/file/game.cpp&s... It's messy and in many ways ugly but it compiles and runs for an eternity.
and then you put the code in a header and everything explodes