Hi Jonathan:

JP>   Applications should only ever store one value in the user INI
JP> file :   the location of their private INI file.

JP>   Applications should never store any other data in the user INI
JP> file.   All other configuration data should be stored in the
JP> application's   private INI file. 

I recall an extensive discussion about this some time ago.  As I
recall, this was the 'conclusion' that was arived at by most.  I have
two points that I would like to submit for comment:

1) I like to use an environment variable instead of an INI entry to
point to my .INI file.  This way, I can install my applications by
simply copying files and editing the config.sys.

2) I much prefer to use text mode .INI files for easier editing.

The thing that has been bugging me about point 1 is that it requires
me to boot my PC.  I'm getting to the point where I get really annoyed
whenever I have to boot my PC.  The user INI file would allow me to
solve this problem, but feel weird about messing with it.

My problem with point 2 is that the code I wrote to handle this (3 C++
classes: Profile, ProfileSection, and ProfileEntry) really bloat out my
code.  The first 2 classes inherit from ISequence, which makes them
fairly expensive in terms of code size.  The OS/2 API adds roughly
nothing to my executible size and probably executes faster.  BTW, I
would be happy to share this code with anyone who is interested.

It would be great if there were standards, or at least prefered method
outlining this sort of thing in detail by a source of authority.  


Best wishes,

Tom

 * KWQ/2 1.2g * Be sure to use DEVICE=EXXON to screw up your environment.

--- GEcho/2 1.20/Pro