On Wed, Nov 15, 2000 at 08:39:09PM +0100, Andreas J. Koenig wrote:
> But IniFile? Why not Win32::IniFile? Isn't it strictly speaking a
> Win32 module? Is there any standard associated with .ini nd .reg files
> tht make it likely or even possible that these file formats will be
> deployed outside Win32?
IniFile was written originally to support .ini file access on Unix
platforms (for the Linux port of Unreal Tournamet). As more and more
Windows programs are being ported to Unices, there is a growing demand
for this kind of routines outside Win32, albeit still uncommon. I think
that when a Unixer looks for tools to access .ini files, it is quite
unlikely for him to look in the Win32 tree as many of the Win32 modules
contain native codes (IniFile is Perl-only). Moreover, Win32::Tie::Ini
already provides .ini access by issuing Win32 calls; if I were to write
a Win32 program from scratch I would use Win32::Tie::Ini because it is
better to make use of native platform facilities.
That said, I would agree to changing it to Win32::IniFile. Please tell
me what you think. Thank you.
--
Avatar
