FindFirstFile() limitations?

  • Thread starter Thread starter tom
  • Start date Start date
T

tom

Hello,

I want to know if FindFirstFile() can do more as I expect.

FindFirstFile() can take the arguement of "*" or "?", for example,
FindFirstFile("result.*.txt", &FileData);


I want to get files result_12.txt or result10.txt only,
Could it be possible that it allows "||"?
For example,can I use the format similar as below:
FindFirstFile("result_(12||10).txt", &FileData);

Thanks,

Tom
 
tom said:
Hello,

I want to know if FindFirstFile() can do more as I expect.

FindFirstFile() can take the arguement of "*" or "?", for example,
FindFirstFile("result.*.txt", &FileData);


I want to get files result_12.txt or result10.txt only,
Could it be possible that it allows "||"?
For example,can I use the format similar as below:
FindFirstFile("result_(12||10).txt", &FileData);
Click to expand...

From the Platform SDK docs on FindFirstFile:
----
lpFileName
[in] Pointer to a null-terminated string that specifies a valid directory or
path and file name, which can contain wildcard characters (* and ?). If the
string ends with a wildcard, a period, or a directory name, the user must
have access to the root and all subdirectories on the path.
 
tom said:
I want to know if FindFirstFile() can do more as I expect.

FindFirstFile() can take the arguement of "*" or "?", for example,
FindFirstFile("result.*.txt", &FileData);


I want to get files result_12.txt or result10.txt only,
Could it be possible that it allows "||"?
For example,can I use the format similar as below:
FindFirstFile("result_(12||10).txt", &FileData);
Click to expand...

Nope. Use

"result*.txt"

and filter the result set as you like. Alternatively, run the search once
against each of the different patterns.

Regards,
Will
 
Back
Top