I did suggest storing the results of conditional expressions in vars. I specifically warn against using direct assignment of conditional expressions to variables, however. In the example, an if statement with the conditional in question is used as the mechanism to determine what values to drop into the temporary vars.

I think we need to be clear here that although VERGE C is similar to C, it is not C. It's more than a stone's throw removed from C, in fact. Assigning the results of conditional expressions directly to variables, nested structs, assignments within conditionals, prefix increment/decrement operators, operator precedence -- these devices are useful and even obvious. To a programmer. Most of the people who use VERGE are not programmers. VERGE C is a scripting language intended for softcore programming. ;-)

VERGE C in V3 is largely similar to (read: based on) VERGE C in V2 (with a few notable exceptions,) and as a result has most of the same rules. Conditionals only within if/while statements being one of them. Everyone can have a good lament over this or that, and some features may be added if their usefulness outweighs the added (compiler) complexity. But for the most part VERGE C is done. Don't expect that what is syntactically sound in C will/must also be syntactically sound in VERGE C.

Think C! Then think of that "eccentric" uncle nobody in the family talks about. He's your uncle, sure. But he ain't exactly proper, if you know what I mean.

My plan for some time has been - right now, int arguments are processed one way, and conditional arguements are processed another. I've always intended to merge the two so conditionals like > and && are just numerical arguements, the reason I haven't done so yet is that it will require a bit of modification to support unary ! which is obviously needed, but the good part is when I get to it, I can support unary minus too. :p