(0002610 - 825 - 865 - 865 - 865 - 865 - 865)
user291
09-05-05 15:48
|
Yes...just continuing from your thoughts a bit. Browsing references to a class doesn't yield subclasses but noone currently expects it to (since such things are easily found in one spot in a hierarchy browser). However finding all users of a trait has no analog to this currently. My original thought was that "references" makes sense for this purpose. Maybe doing so would be inconsistent with class hierarchies but it seems to me to be simple and obvious. Still, I think we should be ready to answer the question "then why doesn't browsing references to a class include subclasses?". We could avoid this by having a menu item (which only appears for Traits) labeled "users". Then "references" would simply be less useful for traits since they are seldom directly referenced in methods. Anyway, just some thoughts... |