[Plugin] AttributeInspector 1.1.1 – 2014-05-08

[Dan Rathbun]

BTW... you can currently use the triple equal method with Length class, so this will work:
true === length_value || false === length_value

[Dan Rathbun]

@aerilius said:

Or shouln't ruby have a "Boolean" super class of which TrueClass and FalseClass are subclasses?
type = (value.is_a?(TrueClass) || value.is_a?(FalseClass)) ? "Boolean" : value.class.to_s

I always wondered why not ?

One thing I have done in the past is create a boolean?() query method for Object (or something else like Comparable.
Now this is frowned upon, and I never released it, just suggested, or had it in my test scripts.

def boolean?()
  is_a?(TrueClass) || is_a?(FalseClass)
end unless method(;boolean?)

---

AND / OR, ... create a Boolean mixin module, and then mix it into only TrueClass and FalseClass. The mixin module may not actually need any additional functionality, at all ?

Then the kind_of? (alias is_a?,) methods will return the appropriate true or false using a Boolean class argument, for any, and ALL objects.
The === will also work for all objects, which makes case statements work:
Boolean === value

---

Whichever one (or both,) ya'll want, would need to be adopted as an API extension, by the community. (And we'd need to convince the Trimble team to add it.)

[tt_su]

The Length class is a bit of a special case. It's trying to be a sub-class of Float - but the Ruby API doesn't really let you do this. So there's some hackery in the background to make it work. I'll file an issue to see if we can avoid the argument error.

[Dan Rathbun]

Thanks TT.

Just returning false would be preferable, instead of raising an ArgumentError (when really TypeError occurs.)

[tt_su]

Yea, there's a few annoying inconsistency where the correct error isn't raised.