Your example: template engine makes the decision on what means True/False.
My example: template engine just tests a Boolean for true/false.
Less magic in mine than yours.
No. V already has this concept that "null = false; notnull == true". That's where the "if( $result ..." comes from: this is the only easy way to handle nulls in V (that i've found so far; the faffing about with trying to simulate "if( x == null )" in V, and support it with users, evetnually made me give up and just use the if() test.
Otherwise...I wouldn't have suggested it. I though it was a good idea because it is actually consistent with design decisions already made in V (which I'm not sure I agree with in the first palce, but now they're there I'm happy to run with them...)
Ha -- well, since the dude who suggested it won't lower himself to login to bugzilla... I doubt you'll see a patch entered by him. <grin>
I've contributed to many o-s projects, but got fed up of the amount of time I wasted creating one million + 2 BZ accounts and mailing list confirmations etc. It's a sign of my delight with V that I (eventually) prodded the company to register on the mailing list (this is a group mailing addresss so it goes to multiple people here).
Frequently, it takes MORE time to register with BZ or the majordomo (espeically with slow confirmation systems) than it does to type uip the damn RFE or bug report! That takes the piss, and I refuse to support this group-think stupidity where every project feels so self-important as to force user-accounts on everyone. The truth is that most of them have no need for it, and are just irritating people; the silent majority who don't contribute because there are just slightly sufficient hurdles to make it a PITA.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
