-=> Quoting Mike Bilow to Jonathan de Boyne Pollard <=- 

 MB> Jonathan de Boyne Pollard wrote in a message to Andrew Grillet:

 JdBP>   If your argument is based on the principle that OS/2 users
 JdBP> are generally   more astute than Windows users, then I can

 [snip]

 JdBP>   Or use one of the 15 or so INI file editors Out There ...

 MB> The problem is what to do in the case of file corruption.  Many INI
 MB> editors and other programs assume that the file is in a valid form or
 MB> they will not work.  With text files, it is considerably easier to
 MB> repair corruption by hand, especially since most such problems are
 MB> created by INI editor bugs in the first place.  I also find that many
 MB> INI editors let you see only one thing at a time, and there is no
 MB> equivalent functionality to what can be achieved by dumping a text
 MB> file to a printer.  Admittedly, many of these things could be looked
 MB> at deficiencies of INI file editor programs rather than of the binary
 MB> file format per se, but they seem equally annoying to the user from a
 MB> practical standpoint.

The INI editor that comes with the book _Real_World_Programming_ has one
of the nicest user interfaces I've seen in an INI editor.

All it can do is delete Application and Key names and Save Changes, but
since it comes with the source it would be possible to modify it to do
more.

I'd prefer binary INI files.  If an INI file gets trashed, whether its
text or binary, I'm not going to try to recreate it by hand. :-)  I'll
restore from backup or install the program again.

Phil - Fido:  1:124/8014.0 | Internet:  phil.crown{at}bluecafe.com

--- Blue Wave/OS2 v2.30