Trick for young players.

[BobJanova]

bool is a value type, so it is in the collection, because false == false.

[BobJanova]

object is not a value type but the thing you've stored in the object is a value type.

[BobJanova]

== will resolve to ReferenceEquals for reference types, and if there is no == operator override. For a value type (like bool) it will do a content equality.

[Jorgen Andersson]

Quite right. I referred to this specific case which of course wasn't obvious at all. :sigh:

People say nothing is impossible, but I do nothing every day.

[Sentenryu]

you clearly are forgetting about polymorphism :laugh: this is just one of the confusions he can cause... (see the << and >> operators in c++)

I'm brazilian and english (well, human languages in general) aren't my best skill, so, sorry by my english. (if you want we can speak in C# or VB.Net =p)

[OriginalGriff]

:thumbsup:

If you get an email telling you that you can catch Swine Flu from tinned pork then just delete it. It's Spam.

[Lost User]

If I may be clear, I understand what is happening and why - the fact remains it is an inconsistency. If each object had two booleans, would it act the same? As an'outside observer' the behavior is inconsistent. In the case where this came up, the framework was processing parameters passed to a constructor, and trying to find the best constructor to use based on the parameters. The routine in question failed if two booleans were passed because e second was deemed to be the same parameter as the first when their values were equal. Because this is a framework, and until now nobody had happened to write a constructor with multiple value types of the same type, and subsequently try to use it with those value types having the same value, nobody had noticed the issue. If lit had been integers rather than booleans it would have been even more interesting - as the chances of the values also being equal wold be that much smaller. So, I under stand what is happening, but I still regard this as an issue with the potential for causing larger problems I an application. The fact that the Contains method works inconsistently depending on the contents of objects is the problem. I ask 'does object a contain object b' And I expect the answer to be yes or no - and not 'well, if it's an object containing only a value type, then the collection contains at least one similar Object where the value type has the same value, but if it's a reference type then that instance exists I the collection' This means in principal that I need to know about the objects in any collection beforehand - which especially in a framework environment, I do not.

MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

[twizzle801]

I see the problem... it's my inability to understand why people prefer object oriented languages. I must be too old to play. :(

[Jorgen Andersson]

Try this:

Sub Main()
    Dim arg1 As Object = True
    Dim arg2 As Object = True

    Dim collection As New List(Of Object)() From { \_
     arg1 \_
    }

    Dim first As Boolean = (collection.Contains(arg1))
    Dim second As Boolean = (collection.Contains(arg2))
    Console.WriteLine(String.Format("{0} {1}", first, second))

    first = False
    second = False

    For i As Integer = 0 To collection.Count - 1
        If collection(i) = arg1 Then
            first = True
        End If
        If collection(i) = arg2 Then
            second = True
        End If
    Next

    Console.WriteLine(String.Format("{0} {1}", first, second))

    Console.ReadKey()
End Sub

At least it's consistent. :-D

People say nothing is impossible, but I do nothing every day.

[Lost User]

I used to think that some years ago - couldn't see the point; until I started using them - and fell in love!

MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

[Lost User]

Contains uses Equals, and it has to. Firstly, because it can't see an overloaded operator==, secondly because if it somehow could, you could put a double.NaN in a list and never find it again - you'd have a list with one element, but Contains is false for any argument, making it look as though the one element isn't any one value, and thirdly because object.ReferenceEquals would always give false for lists of value types because you'd create new boxed objects all the time. So there's really no good alternative, it has to be this way.

[BobJanova]

_Maxxx_ wrote:

If each object had two booleans, would it act the same?

Depends if it's a value type, and whether Equals is overridden.

_Maxxx_ wrote:

The fact that the Contains method works inconsistently depending on the contents of objects is the problem.

It does not behave differently depending on the contents. It depends differently depending on the type. You can think of it like string interning: there is only one false so when you have two of them, they are always equal, both in value terms and in reference terms. I think this is true for all value types; it's certainly true for all basic types.

_Maxxx_ wrote:

And I expect the answer to be yes or no - and not 'well, if it's an object containing only a value type, then the collection contains at least one similar Object where the value type has the same value, but if it's a reference type then that instance exists I the collection'

The answer is yes if there is an object in the collection for which Equals with the one you've passed returns true. That's what equality means, and it's usually much more useful than checking for reference equality. You can override == on custom types to make that check whatever you want. By default the behaviour is to check references for reference types and to check values for value types (or at least base types). Choosing which constructor to use based on the values of parameters, instead of the types of parameters, is a WTF all to itself. Edit: Equals, not ==. I always override both of these, and also !=, if I do either, so I get them mixed up sometimes.

[BobJanova]

Like all tools, it is excellent when deployed correctly and a useful technique to know about. It's over-promoted in modern CS though, in my opinion, to the detriment of other useful techniques like functional or event-driven programming.

[JMK89]

Gotta love ReSharper

static void Main()
{
object arg1 = true;
object arg2 = true;

var collection = new List<object> { arg1 };

var first = (collection.Contains(arg1));
var second = (collection.Contains(arg2));
Console.WriteLine("{0} {1}", first, second);

foreach (var t in collection)
{
    //Do fuck all
}

Console.WriteLine("{0} {1}", false, false);

Console.ReadKey();

}

[Lost User]

BobJanova wrote:

Depends if it's a value type, and whether Equals is overridden.

Not sure I even follow you there. An object with two boolean properties is not a value type - or am I misunderstanding you?

BobJanova wrote:

and it's usually much more useful than checking for reference equality.

I have to disagree there, and say it entirely depends on the context. If I want to check if two objects are the same object, i would like to be able to do so in a consistent manner, without having to check to see if the object is a value-type wrapper. similarly, if I want to check if the value of two objects are the same, I would expect to be able to use the same methods regardless as to whether the objects in question have booleans or Customers internally. I reiterate - I understand exactly what is happening, and it is a trick for young players (hence the post). But I still think that there is an inherent (pun absolutely intended) discrepancy n the handling of boxed objects vs the handling of 'vanilla' objects.

BobJanova wrote:

Choosing which constructor to use based on the values of parameters, instead of the types of parameters, is a WTF all to itself.

The AIM of the method in question was was to decide on the constructor based upon the TYPES of parameter vs TYPES of arguments. The parameters were in a collection and the arguments in another.

1. For Each parameter in the constructor it is checking
2. For each argument in the collection
3. If THIS ARGUMENT is already in our output collection, continue
4. If this argument is of the same type (or subtype etc) as the current parameter, add it to the output collection
5. Next Argument
6. Next parameter

Line 3 is where the issue arises, because if there are two value arguments, and they both have the same runtime value, then this If is triggered and the argument ignored for the 2nd and subsequent parameter.

MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

[Florin Jurcovici]

That's exactly the opposite of what would seem reasonable to me.

[BobJanova]

_Maxxx_ wrote:

An object with two boolean properties is not a value type

Depends whether you want it to be.

struct MyType { public bool a, b; } // value type
class MyType { public bool a, b; } // reference type

_Maxxx_ wrote:

If I want to check if two objects are the same object, i would like to be able to do so in a consistent manner, without having to check to see if the object is a value-type wrapper. similarly, if I want to check if the value of two objects are the same, I would expect to be able to use the same methods

You can. ReferenceEquals and ==/Equals respectively. Contains is defined to use Equals not ReferenceEquals because that's almost always what you want when there is a difference.

_Maxxx_ wrote:

The AIM of the method in question was was to decide on the constructor based upon the TYPES of parameter vs TYPES of arguments.

Then why is it using the values? Capital letters don't change what you are actually coding (or what your pseudo-code does). Line 3 is where the issue arises because you shouldn't be doing that; the value of an argument is irrelevant to the parameter matching to find a method.

[Lost User]

BobJanova wrote:

Then why is it using the values?

It's not. It's using contains in an attempt to determine if the collection contains the object it is looking at. As it turns out, a (very small minority) of the objects are boxed value types, and an even smaller number of these have the same value, and so 'break' the code. The fact that Contains uses the values rather than comparing object references is exactly the cause of confusion. Asking why is it using values is like asking someone who has accidentally shot off their toe "why did you fire the gun at your foot?"

BobJanova wrote:

Capital letters don't change what you are actually coding

Actually they do in C#, which is case sensitive ')

BobJanova wrote:

(or what your pseudo-code does).

The capitals were there for emphasis and to help understand which bits I was TALKING about

BobJanova wrote:

Line 3 is where the issue arises because you shouldn't be doing that;

No shit, Sherlock? I know that is the bit that's causing the problem.

BobJanova wrote:

the value of an argument is irrelevant to the parameter matching to find a method.

Yes - and as I said, the AIM of the code was to check for the presence of the argument, not its value. I capitalised there for emphasis

MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')

[englebart]

I think the point is... Why would you ever need more than one instance of true or false? The boxing must create a new instance. New instance means more overhead. SmallTalk has a great answer for this: abstract class Boolean {...} class True extends: Boolean { // singleton } class False extends: Boolean { // singleton } You can imagine how easy it is to implement all of the logical operators with this construct! True.OR(Boolean that) { return this; } True.AND(Boolean that) { return that; } False.OR(Boolean that) { return that; } False.AND(Boolean that) { return this; }

[Harley L Pebley]

_Maxxx_ wrote:

An object with two boolean properties is not a value type

Depends on the type of the object and what you mean by "object". Here's a variation on your original post:

using System;

namespace ClassVsStruct
{
class Program
{
class CBool
{
public bool Value1;
public bool Value2;
}

    struct SBool
    {
        public bool Value1;
        public bool Value2;
    }

    static void Main(string\[\] args)
    {
        var c1 = new CBool { Value1 = true, Value2 = true };
        var c2 = new CBool { Value1 = true, Value2 = true };
        Console.WriteLine("Equals: {0}", c1.Equals(c2));

        var s1 = new SBool { Value1 = true, Value2 = true };
        var s2 = new SBool { Value1 = true, Value2 = true };
        Console.WriteLine("Equals: {0}", s1.Equals(s2));
    }
}

}