It's worth considering how truth is evaluated in LOLCODE.  Some languages consider all objects true (except whatever object represents falsehood).  So this would allow objects to be interpreted in a boolean context as true.

Also, in order not to avoid using "true" and "false" as keywords, alternatives should be found.  My personal suggestion is that Truth could be represented with the value "K" (which would be similar to LISP's "T").  Falsehood as "false" or "nil" seems kind of ugly, and could be represented with something like "NOES" or "PWND".

//- silverskein 2007/05/30 21:07 //

I think true could be ROXORZ and false could be SUXORZ. Also IMHO..OMFG..KTHX could be another for alternative IF...THEN..ELSE 

	HAI
	I HAS A NOOB ITZ SUXORZ
	IMHO NOOB ROXORZ
		VISIBLE "teh noob pwnz u!"	
	OMFG
		VISIBLE "noob iz 4ver a nab!"
	KTHX
	KTHXBYE

 --- //jana, 2007/05/30 21:53//

jana, I don't think that's very appropriate for lolcode; that's more 1337speak.

OK, I assume I am not yet completely into the spirit of the whole thing. I thought that, because of the page head banner says "I has 1337 CODE.", 1337speak would be ok. I hope I'll figure the boundaries of both intersection and disjunction of this lolcat thing and 1337speak. 
Maybe just SUX and ROX could be ok?

 --- //jana, 2007/05/31 05:32//

This is easy. Boolean true is WIN, false is FAIL.

 --- //ritontor, 2007/05/31 17:36//