| Ticket UUID: | 1059897 | ||
| Title: | [info procs] & [info commands]: inconsistent search | ||
| Type: | Bug | Created on: | 2004-11-04 00:14:49 |
| Submitter: | dgp | Assigned to: | dkf |
| Subsystem: | 17. Commands I-L | Severity: | Minor |
| Priority: | 3 Low | Last modified: | 2013-09-10 18:55:05 |
| Status: | Open | Closed by: | nobody |
| Resolution: | None | Closed on: | |
| Version: | obsolete: 8.5a2 | ||
| Description: | ||||
test info-15.8 documents the "knownBug" that [info procs $unqualifedName] searches only the current namespace, while [info commands $unqualifiedName] also finds matches from the global namespace. Besides being inconsistent, it seems to be at odds with the documentation as well. | ||||
| User Comments: | ||||
dkf added on 2004-11-04 22:23:18:
Logged In: YES user_id=79902 Documentation says [info commands] is wrong. dkf added on 2004-11-04 22:28:39:
Logged In: YES user_id=79902 Or rather documentation is deliberate vague round here, with a side-helping of "probably also wrong". This would all be easy to fix if I understood what was actually supposed to happen, for both [info commands] and [info procs] in these four cases: No pattern Simple (::-free) pattern Pattern with non-leading :: Pattern with leading :: dkf added on 2005-04-29 21:21:09:
Logged In: YES user_id=79902 OK, I now know more about what's going on in this area of "pattern" matching. 1) No pattern is always the same as pattern==* 2) Pattern without namespace results in search of things visible right now 3) Pattern with namespace results in search of things actually in that namespace info commands is rather like info vars in its behaviour, except that variables and commands have different general resolution rules. info procs always works within the context of the current or named namespace. dkf added on 2013-09-10 18:55:05:
Been this way for ages; fixing cannot be urgent! | ||||
