True and false aren't defined
Summary:
Reposting from email:
_if appears possibly broken. In a test case where I have the following in
Display text:
false branch
true branch
I get the output:
false branch
false branch
Ah -- yeah, that's one of the famously missing features, that I've been
working around. What's catching you up is the fact that "true" and "false"
aren't actually defined. So they are both evaluating to Unknown Name,
which probably evaluates to false in this context. (Haven't tried it, but
that would make sense.)
Please just log a Missing Feature against this -- it's one I've been
meaning to deal with for ages, and simply haven't gotten around to, for no
particularly good reason. (I suspect that it'll take me all of an hour to
add.) I need to decide whether to name these True and False, or _true and
_false, but I suspect that in this case it's not a bad idea to make True
and False reserved words.
Marking this one as High Priority mostly because it is easy low-hanging fruit. And while it can be worked around, it's a headache to do so. Might as well just deal with it...
Justin: okay, we now have True and False defined at the system level. These are technically Things that evaluate to the appropriate values, but you can basically treat them as system constants.
(Technically, you can override them in a Space. I don't recommend doing so, but Querki does give you enough rope to hang yourself if you are so motivated. We might eventually add the ability to create a non-overrideable Thing, so that we can reserve words, but for now we're leaving that to convention.)
