Feature request: Implement FILTER MATCHES PATHNAME for FILING.LIST

[nbriggs]

If you ask Interlisp to enumerate files with, for example, names starting with "C" in a top level folder it will generate the following sequence of operations:

FILING.LOGON[binchicken: (SIMPLE (6 26721 30561 27745 3 25701 30208 6 25202 --)) (21552)] => (25975 
2944 21552)
FILING.CONTINUE[#<Filing Session on binchicken:dev:hawala/136,120710>] => 60
FILING.OPEN[NIL (0 0) NIL #<Filing Session on binchicken:dev:hawala/136,120710>] => (25975 2894)
FILING.GET.ATTRIBUTES[(25975 2894) (3 4 5 21 16 17 18) 
#<Filing Session on binchicken:dev:hawala/136,120710>] => ((CREATED.ON -2147483648) (FILE.ID (0 0 0 0 
0)) (IS.DIRECTORY T) (PATHNAME "!1") (SIZE.IN.BYTES 0) (FILE.TYPE 1) (VERSION 1))
FILING.LIST[(25975 2894) (21 5 27 16 3 2) ((FILTER (MATCHES (PATHNAME "lispusers/C**"))) (DEPTH 1)) 
NIL #<Filing Session on binchicken:dev:hawala/136,120710>]{bulk data} => NIL

There is a top-level directory on BinChicken, Lispusers, in which there are many files starting with "C", but this "filter matches pathname" expression does not return any files. It doesn't matter whether the DEPTH parameter is 1 or greater.

[devhawala]

Good evening,

the matches/pathname scope-filter is now implemented for find()/list() in the current version of Dodo just committed. The implementation should be fairly complete, including multiple path segments with patterns, **-Wildcards for "multiple components" and lowest/highest in addition to exact/any version specs per path segment.

The logging of the find() procedure is a bit verbose to see which pathname-pattern was sent to the file service, how this path was splitted and transformed from Xerox-wildcards to regex-patterns for the pathname-segments and finally the files found with this pathname-pattern. The pattern segments are interpreted in reversed order when searching for match candidates and logged in this order.

I tested it internally with the examples given in page 29 of the Filing-Protocol spec. (May 1986), rebuilding the sample directory structure under {fs1:}public in the delivered sample file service, all filters in the examples worked as described.

See also the hints at the end of the File Service Configuration page about the maxDepth parameter.

Greetings, Hans

[nbriggs]

Thank you for this -- it's working well for Interlisp.