* additional argument for "info precedence": "-intrinsic" Syntax: <objName> info precedence ?-intrinsic? ?pattern? If "-intrinsic" is specified, only the classes of the superclass type hierarchy are returnd. Otherwise, the precedence contains mixin classes as well. * Remove pattern argument from "info class" * Check results for guards to be boolean instead of integer (now, guards are allowed to return e.g. "true") * Bump version number to 1.6.1
* Continued with info orthogonality change <object> info mixin ?pattern? <class> info instmixin ?pattern?
?pattern? behaves exactly like in the change of two days ago. Preceding colons in the name of the queried class are not required.
Still to do "-closure" in
<class> info instmixin -closure ?pattern?
* In all mentioned calls, where pattern refers to an object/class and it contains wild-cards, a preceding :: is added automatically to the search pattern, if it is missing. Since all object names start with ::, an omitted leading :: in a search pattern is an obvious mistake
* Made the behavior "pattern" in the following calls identical concerning wild cards and object lookups