🚀 go-pugleaf

"Hans Galema" <dontusethis@dontusethis.nl> wrote in message
news:408e0d6a$1@newsgroups.borland.com...

> Well if you read my post again then you will see that I reported
> that FileExist DOES support wildcards. And that amazes me. The
> help does not state it. FileExists would even find Unit1.cpp for
> FileName == "*nit.?".

Upon further examination, FileExists() calls FileAge(), which in turn calls
FindFirstFile(), which then returns the first filename matching the
specified mask.  FileExists() is not meant to support wildcards, it is
merely a side-effect due to Microsoft's own API design.

> No I do not need wildcard matching. I need a file exist
> function that reports if a file for a filename exists.

That is what FileExists() does.

> The '?' in my filename was unintentionally, caused by the
> fact that the filename was generated by code.

Then you will have to validate the filename to see if it contains any
invalid characters before then testing for its existance in the file system.
Otherwise, stop using buggy generated code in the first place.

> The intention of using FileExist was to get a false for
> unvalid filenames. To my surprise FileExist does not
> care for unvalid filenames, but allows wildcards in them.

See my comments above.

> Until now, my experience was that FindFirst/FindNext
> could NOT be used with wildcards.

On the contrary, they are used very often for enumerating the file system
specifically using wildcards to find desired files.


Gambit