View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000684 | LDMud 3.3 | Efuns | public | 2009-10-01 16:33 | 2009-10-04 08:17 |
Reporter | zesstra | Assigned To | zesstra | ||
Priority | normal | Severity | minor | Reproducibility | N/A |
Status | resolved | Resolution | fixed | ||
Target Version | 3.3.720 | Fixed in Version | 3.3.719 | ||
Summary | 0000684: get_dir(): listing directory contents does not work according to documentation | ||||
Description | The get_dir() efun has a few inconsistencies. One is: get_dir("/",...) returns the _contents_ of the root directory. get_dir("/some/other/path/",...) will not return the contents, but the directory "/some/other/path" itself. Additionally, the man page states: To query the content of a directory, use the directory name with a trailing '/' or '/.', for example get_dir("/path/."). Use the directory name as it is to get information about the directory itself. But neither a trailing '/' nor a trailing '/.' does work, because they are stripped off by get_dir. You have to use "/some/other/path/*" for path not being the root dir of the mudlib. So, unfortunately, changing the behaviour to be a) consistent and b) according to documentation will probably lead to compatibility problems, as Gnomi already pointed out in a private discussion. So, I want to record the issue here and document the decision: adapt the behaviour to the documentation or change the documentation to the inconsistent behaviour? | ||||
Tags | No tags attached. | ||||
|
I believe the efun works as described, but with a twist: The path being used is the one returned from valid_read() in the master. That fact should be documented. (In our mudlibs, valid_read() does path normalization, 'breaking' get_dir) |
|
Very good point, that seems to be the reason. *argl* For "/" it works, because that is then stripped to "" and "" is converted to "." which is interpretated as the mudlib root directory itself. I guess, I have to fix some mudlib, there is no real reason not to conserve the trailing /. ;-) But I agree, that the documentation has to be improved. |
|
I added a note about the path normalization to the manpage in r2752 and r2753. |
Date Modified | Username | Field | Change |
---|---|---|---|
2009-10-01 16:33 | zesstra | New Issue | |
2009-10-02 13:01 | fufu | Note Added: 0001430 | |
2009-10-03 16:33 | zesstra | Note Added: 0001441 | |
2009-10-03 16:33 | zesstra | Assigned To | => zesstra |
2009-10-03 16:33 | zesstra | Status | new => assigned |
2009-10-04 08:17 | zesstra | Note Added: 0001446 | |
2009-10-04 08:17 | zesstra | Status | assigned => resolved |
2009-10-04 08:17 | zesstra | Fixed in Version | => 3.3.719 |
2009-10-04 08:17 | zesstra | Resolution | open => fixed |