|
|
Post by Jo on Jul 13, 2015 9:20:27 GMT -5
File Pattern *.asm does not find files a.b.asm in FileManager and in FileLists. Files with just 2 levels (a.asm, b.asm) are found, but 3-level-files are not found. The Windows Dir-Command (Dir *.asm) would find all files (a.asm, a.b.asm, b.asm).
Jo
|
|
|
|
Post by George on Jul 13, 2015 13:42:33 GMT -5
Jo: Hmmm, have to have a look.
George
[Update]
The code is doing what the Doc. says ("Working with File Manager"), but I have to agree that the action is not the same as Explorer.
The SPFLite definition of * is that it matches 0 or more characters up to the next character specified in the mask. The period is not treated in any way more special than any other character that might have been entered.
Therefore *.ASM would match A.B.ASM up to the A. and then of course ASM fails to match B.ASM.
I guess the safest change to make would be to treat the . as a special case, and if present following an *, to take it as meaning skip up to the last period in the filename.
George
P.S. You could of course temporarily code *.ASM;*.*.ASM;*.*.*.ASM ;-))
[Update]
OK, next release will handle it as I described above.
George
|
|
|
|
Post by Jo on Jul 14, 2015 10:11:41 GMT -5
George: Thanks. And yes, I added *.*.ASM in my FileList ;-))
Robert: There seems to be an API, because REXXs SysFileTree utility-function finds all files that match a file specification and "SysFileTree uses operating system APIs to find the files". (ooRexx Doc)
And I remember when IBM added wildcard-support to RACF datasetnames. The first attempt was not very successful, later they added egn (enhanced generic names) with ** matching anything including dots.
Jo
|
|
|
|
Post by George on Jul 14, 2015 10:15:46 GMT -5
Jo: Yes, the standard APIs handle this quite well. But when we added the enhanced masking ability to FM, the normal API couldn't be used and had to be replaced by our own code. It was that private code that didn't quite follow the Explorer standards for *. handling.
George
|
|
