View Task #571
Summary: Add glob_path for interp and request
| Difficulty:
1 |
|
Version goal:
1.3x |
|
| Status:
Unassigned |
|
Description
Now that the resolver's glob_path has become more inconvenient (it must be passed a list of component roots), we should provide
$interp->glob_path("/foo/bar/*")
$m->glob_path("foo/bar/*") # can be relative to current component
This is a natural extension to $m->comp_exists.
History
| Oct 28, 2004 01:36 PM |
|
Jonathan Swartz created task.
|
| Oct 30, 2004 08:23 PM |
|
Dave Rolsky
writes: If it's going to be a method that's more exposed than it is now, can we redo the API a bit and make it take a regex? And if we do that we should change the name.
|
| Oct 31, 2004 05:15 PM |
|
Jonathan Swartz
writes: That would be nice, but...glob_path for a file resolver can be implemented efficiently on glob (obviously), and for a database resolver can be implemented with standard SQL wildcards. Can you think of an efficient implementation for a file resolver if it took an arbitrary regex, other than testing every filename underneath each component root?
|