Why is there no Bool Type?

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

FlameDuck

and then this wouldn't work

Maybe not, but this would:

Select moo
Case True
	Print "moo is True"
Default
	Print "moo is False"
End Select
End

Anyhow since you're dealing with a boolean type, there not much point in making a select statement. Just go

If moo = True
	Print "moo is True"
Else
	Print "moo is False"
End If

Since you *know* for a fact that moo is supposed to be a boolean, and then by definition only has 2 states, there is no need for any extra logic to determine what number it actually is - all that's important is that it isn't 0 (aka. True).

Constraints are mostly expresed as booleans in visual models.

In my experience they're mostly expressed as states, as in "you're allowed to do this, if you're in this, this or this state" but I suppose different people model things differently.

And as ENAY says, you save 7 bits :)

No. Fetching a byte is actually slower than fetching an int. Shifting and anding a byte, to get the bit you want is even slower.