I'd back this, after all they refer to logical states which are "black and white", either always correct or never correct. No half-way "maybe correct, etc." Replace 'correct' with fulfilled depending on the context.
(Just CentiAEuro-pinching: I'm think its spelt fulfilled, one 'l' the first time, two 'l's the second time.)
Maybe someone who plays with logical algebra will have a better answer?
Grant
At 4:46 PM +0200 31/3/03, Peter Gerwinski wrote:
Frank Heckenbach wrote:
When updating the documentation, Peter N Lewis and I came to the problem how to describe the Boolean values `True' and `False'.
Peter suggested "true (conforming to reality) and false (different from reality", but I think "reality" is not a good term here (what do computer programs have to do with reality, anyway ;-).
What about this?
"True" stands for a condition which is always fullfilled - such as "2 = 2" - and "False" stands for a condition which is never fullfilled - such as "1 = 0".
Formally spoken, "condition" ties it "too much" to the usage in "if" statements etc. - but this is what Boolean values are used for in reality. ;-)
In order to illustrate that other uses are possible at all, an example with a Boolean variable should follow.
Just my 2 CentiEuro,
Peter-- WARNING: Do not execute! This software is patented! See: http://swpat.ffii.org/patents/txt/ep/0394/160/
echo -ne PROGRESS\r;for i in `seq 8`;do sleep 1;echo -n %;done;echo