>It's really difficult to make the transition to
resource-rich
>applications... it's hard not to count clock cycles, measure stack
>penetration (do people even *know* how deep the stack needs to be on modern
>desigs? Or, do they just keep bumping it up until the code works??), pare
>data down to the smallest necessary size, etc. (I still cringe every time I
>use an int for a bool! :>)
I wouldn't want to waste 32 bits for a simple boolean data type. But I
also wouldn't try to cram 8 booleans into a byte. The and'ing and
or'ing you have to do isn't worth the space savings, unless your data is
primarily on/off.
Everything depends on the situation.