Why overload true and false instead of defining bool operator?

As the docs say, overloading true and false is intended to support (nullable) database-types (Yes/No, Y/N, 0/1, etc).

As the docs say, overloading true and false is intended to support (nullable) database-types (Yes/No, Y/N, 0/1, etc). And of course you can define them inconsistently, as with any operator. It is your responsibility to return something sensible.

The compiler goes no further than requiring neither or both.

Thanks - I didn't get that far in MSDN - I started looking elsewhere after their operator overloading page, which wasn't much help. I suppose I didn't think about the fact that you can overload ==/! = the same way, where they conflict with each other, I just could never imagine actually doing it.

Thanks for the tip. – Joe Enos Apr 19 '10 at 22:04.

I had no idea these operators existed. That means you can implement the self-negation paradox: public class ThisClassIsFalse { public static bool operator true(ThisClassIsFalse statement) { return statement? False : true; } public static bool operator false(ThisClassIsFalse statement) { return statement?

True : false; } } So now we know the true solution to this classic paradox... StackOverflowException.

Public bool ThisMethodReturnsFalse() { return true; } – Joe Enos Apr 20 '10 at 4:20.

Depending on the system, true can be any non-zero value. In others, it can be any positive value. Other systems aren't truly boolean, and allow a third state null or nill for the boolean values, which is why you might overload true and false, versus overloading a single bool operator.

This is specifically for . NET, so are you saying that it's for . NET applications talking to non-.NET code?

– Joe Enos Apr 19 '10 at 21:35 Joe, this is a feature in the specification for C#, not .NET. C# could be used in any system, and true and false might need their definition changed. – Benjamin Anderson Apr 20 '10 at 14:18 Benjamin: Thanks for the response - a few comments: First, I believe this is the case for other .

NET languages, not just C# - VB. NET has special operators IsTrue and IsFalse which seem to be the same thing, unless I'm mistaken. Also, you mentioned that C# could be used in any system - I've heard a few people say things like this in the past, but I've never heard explanations.

Other than Mono, is there any other place outside of . NET where C# is actually used? Thanks – Joe Enos Apr 20 '10 at 15:45 Mono is the primary alternative implementation of C#, but C# the language is an open ISO standard, and can be used and implemented by anyone that wants to do the work to implement it.

– Benjamin Anderson Apr 20 '10 at 20:25.

I've seen people overload the true and false overloads in order to do clever things like building expressions in . NET 2.0, before Linq existed. Ayende worked out a syntax like this to build Nbernate criteria queries, using his NHQG project: return Repository.

FindAll( (Where.Publisher. Name == name) && (Where.Publisher. City == city)).

Ahh, the days before LINQ...Those were innocent times when people did atrocious things that were clever at the time... – Joe Enos Apr 19 '10 at 22:08.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.