But again, in CF the implicit coersion is VERY important. If there weren't implicit coersion (or CF was strongly typed, depending on how you want to say it), then there would be no need for an boolean XOR operator, as NEQ would suffice. But that's not the situation we're in with CF, so XOR is needed.
cheers, barneyb On 11/4/05, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>However, they are not equal. So, > (1 XOR 2) != (1 neq 2) > > Exact again, but XOR is rarely used, and even more rarely used on non > boolean, actually, 1 XOR 2 just does not make sense > if 1 and 2 are not booleans. > Normally, one would use boolean1 XOR boolean2, and in THIS situation > (only), boolean1 XOR boolean2 is equivalent to > boolean1 NEQ boolean2 > -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 100 invites. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:223304 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
