🚀 go-pugleaf

"Jos�" <jose@127.0.0.1> wrote in message 
news:qa5on3d6p24qit5hic73bl397a6pg4b9i3@4ax.com...

> Well yes, you are right again. But I am pretty stupid, I do not
> consider reading the documentation of CreateFile() when I do
> not want to create a file.

The documentation for GetFileTime() says the following:

    hFile
        A handle to the file or directory for which dates and times are to 
be retrieved. The handle must have been created using the CreateFile 
function with the GENERIC_READ access right. For more

Besides, you posted your original question in the Win32 API newsgroup to 
begin with, so you got an answer related to the Win32 API.

> Besides, I always use fopen() to open or create a file.

Like I said earlier, the C runtime (which you are using to open the file in 
the first place) has its own functions for retrieving file information - 
stat() and fstat().  You can't really mix APIs like you arte attempting.  If 
you open a file (or any other resource) using the C runtime, then you have 
to use the C runtime to work with it.  If you open a file/resource using the 
Win32 API directly, then you have to use the API to access it.

> Actually, I find it even more stupid to name a function CreateFile()
> if it can be used to open an existing file.

CreateFile() is not creating a file itself.  It is creating a "handle" to 
the file, so there is always a resource creation occuring.  How the handle 
interprets the actual file depends on the flags passed to CreateFile(). 
There MAY be a file creation occuring as well, but only if the function is 
told to do that.

The same argument can be said of fopen(), though.  It is able to create new 
files even though its name suggests it can only open them.  There is no 
separate fcreate() function.  You have to tell fopen() whether you are 
opening an existing file or creating a new file.  The same applies to 
CreateFile().


Gambit