An introduction.
2 messages in this thread
<sigh> It was about 5 or 6 years ago that everyone was lamenting the
_addition_ of INI files to the already deplorable state of CONFIG and AUTOEXEC
files in PC computing.
The NT registry is a cool and beautiful thing. Everything you want to know
about your system is accessible from a single location; no more sysedit with
all those bloody windows but not one of them WORD6.INI. Changing/adding values
in the registry can have immediate results. All your programs can access and
share the information in it, or build on it, knowing their affecting the
_current_ state of the machine. In fact, programs running on other computers
can access and share the information in it, or build on it. And it's really
_fun_ to write code that does just that.
Once you get the hang of it, managing a database is way easier and less
problematic than maintaining a bunch of text files. ASCII is archaic. The INI
is dead, dead, DEAD.
Hurrah!
Patrick.
I certainly know the downside of ASCII INI files, too. Although I haven't had
to add WinNT-specific registry code to any apps I've worked on, I don't even
know where the registry info is kept, and I doubt I can load it into a text
editor. That's what I meant about simplicity of ASCII INI files. Why, even
Unix has ASCII "dot" files for configuring everything under the sun. 🙂