INI file functions

[MSLx Fanboy]

Is there a reason why file handles are not acceptable for INIRead and INIWrite functions?

;;This works

$output = IniRead("C:\Windows\avrack.ini", "Settings", "Volume", "")
MsgBox(0, "test", $output & @CRLF & @ERROR)

;;This doesn't
$file = FileOpen("C:\Windows\avrack.ini", 0)
$output = IniRead($file, "Settings", "Volume", "")
$output = IniRead("C:\Windows\avrack.ini", "Settings", "Volume", "")
MsgBox(0, "test", $output & @CRLF & @ERROR)
FileClose($file)

[Gigglestick]

Possibly because the FileOpen already has the file open, so the parts of IniRead/IniWrite that open the file are blocked?

Edit: They'd be stepping on each other's I/O.

Edited August 30, 2005 by c0deWorm

[Josbe]

Is there a reason why file handles are not acceptable for INIRead and INIWrite functions?

;;This works

$output = IniRead("C:\Windows\avrack.ini", "Settings", "Volume", "")
MsgBox(0, "test", $output & @CRLF & @ERROR)

;;This doesn't
$file = FileOpen("C:\Windows\avrack.ini", 0)
$output = IniRead($file, "Settings", "Volume", "")
$output = IniRead("C:\Windows\avrack.ini", "Settings", "Volume", "")
MsgBox(0, "test", $output & @CRLF & @ERROR)
FileClose($file)

<{POST_SNAPBACK}>

Why do you need the handle for read an INI file?

Simply, just compare the documentation: About IniRead page says :

IniRead ( "filename", "section", "key", "default" )

not like FileRead , the syntax is:

FileRead ( filehandle or "filename", count )

Mainly, IniRead wasn't designed for use file handles.

[/dev/null]

Is there a reason why file handles are not acceptable for INIRead and INIWrite functions?

because IniRead() and IniWrite() are not implemented to accept a file handle. See source code script_file.cpp AutoIt_Script::F_IniRead.

Cheers

Kurt

[MSLx Fanboy]

I know according to the help file that one says that file handles are permitted the other does not. My question is, Why not?

If I can start learning more advanced C++ programming techniques, I might try to work on that code (just a wee bit).

[Valik]

I know according to the help file that one says that file handles are permitted the other does not.  My question is, Why not?

If I can start learning more advanced C++ programming techniques, I might try to work on that code (just a wee bit).

<{POST_SNAPBACK}>

The INI functions wrap underlying INI-related Windows API calls. Unless you are prepared to write your own INI reading/writing code and re-implement all of it, there is no point (or sense) in making the INI functions accept a file handle.

[MHz]

I know according to the help file that one says that file handles are permitted the other does not.  My question is, Why not?

<{POST_SNAPBACK}>

Writing to an INI file is similar to writng to registry. Both IniWrite and RegWrite are more related to each other then as to FileWrite. You cannot have a handle for RegWrite? So IniWrite should not have one.

[Valik]

And to confirm what MHz says, Microsoft agrees since they list the API functions for writing to INI files under the Registry section.

[JSThePatriot]

Well to further concrete the idea of INI and Registry being related...

Before the Registry there were INI files. They became very numerous, and Micro$oft wanted a central place to configure applications. They came up with what is known to us today as the Registry.

*Disclaimer* Micro$oft may not have come up with the 'registry' idea, but they are certainly using it.

JS

[MSLx Fanboy]

Ok, thanks, that would explain why. I'll stick with the existing code...