05-24-2018 10:28 AM - edited 05-24-2018 10:29 AM
OK, I realize that this thread is going on 8 years old. But seriously. Other languages have solved this problem quite a long time ago. The answer is to specify a comparison operator and allow classes to override it.
Labview will never be taken seriously as a programming language while you guys poke around and bluntly state that a problem is not a problem.
05-24-2018 10:46 AM - edited 05-24-2018 10:46 AM
Yes, old post.
As an avid critic of a lot of stuff in LabVIEW I don't like, I fail to see this as being a major reason why people might or might not take LabVIEW seriously. There's a lot more viable reasons.....
That being said, perhaps flattening an object to XML could provide a work-around as this at least includes the namespace of the object.....
05-29-2018 04:29 AM
Gentlemen
It was bug and it was fixed in LabVIEW 2012. http://www.ni.com/product-documentation/14226/en/
Peter