On Tue, Jan 26, 2010 at 08:14:50PM +0000, John Horne wrote:
> > Now I can't see anything in the documentation that suggests
> > nwildlsearch will try to open a file for a line/key stating with "/"
> >
> It's difficult to say whether this is a bug in the nwildlsearch
> processing or not, or whether it is an unusual situation that simply has
> not been documented.
Looks like a mismatch between the code and the spec.
The spec says of n*wildlsearch:
1. The string may begin with an asterisk to mean "ends with".
...
2. The string may begin with a circumflex to indicate a regular
expression.
...
3. Although I cannot see it being of much use, the general matching
function that is used to implement (n)wildlsearch means that the string
may begin with a lookup name terminated by a semicolon, and followed by
lookup data.
In fact (if I'm reading the code correctly), n*wildlsearch turns each key in the
file into a one-item string list, and then applies list matching on that. It
appears that "10.3. File names in lists" applies here, but (to me) it's
unclear what other parts of section 10 apply. Section 10 is entitled
"Domain, host, address, and local part lists" - note NOT string lists.
Or I could be reading the code completely incorrectly :-)
--
Dave Evans
http://djce.org.uk/
http://djce.org.uk/pgpkey
