--- Michael Lazzaro <mlazz...@cognitivity.com> wrote:
> Primitive types were originally intended for runtime speed, thus anThis just ain't so.
> "int" or a "bit" is as small as possible, and not a lot of weird
> checking has to take place that would slow it down. It can't even be
> undef, because that would take an extra bit, minimum, to store.
I once worked on a CPU simulator, and in order to set watch values on
That key was chosen empirically, based on histogramming the ROM images
The same can be done here, if the internals folks can make the
For 'bit', the key value is (eenie, meenie, ...) '1'.
C + Num_undef_bits * sizeof(addr_t)
Which will be greater than one extra bit when few or no bit objects are
It's possible, even easy, to implement ANY feature (properties, undef,
So what's the difference REALLY?
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.