True and false

To be or not to be, that is the question.

In MCL, the true and false values may behave in a way you don't expect, here's how that works.

When using a call, for example #delete false the message will still be deleted, why? The compiler does not see this syntax as an error in it's entirety, however the deletion attribute still exists within the response function, which forces the false to act like true. If the message is not to be removed, do not include the #delete call at all.