How to reading and writing INI files using borland C++ 6.0?

Question

3.00/5 (1 vote)

See more:

Can anyone give me or provide me with a link as to how to use to create and read an ini file in borland C++ 6. I have inherited some applications developed in C++ borland 6 that read and write to the registry and my boss wants that to change to ini files or another method. I can only think of ini files, but any files will do.
Can anyone help me?

Posted 5-Apr-11 23:24pm

Privesh

Updated 5-Apr-11 23:33pm

CPallini

v2

Add a Solution

Comments

[no name] 6-Apr-11 7:51am

You can use text formated file to save program settings and data.
Each line in the file consist of parameter name, tabulation symbol and parameted value.

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kurt Degiorgio · Answer 1 · 2011-04-05T23:55:00

Solution 1

take look at this article the code is plaform independent as such it should suite your purposes:

http://www.codeguru.com/Cpp/misc/misc/article.php/c233/[^]

Posted 5-Apr-11 23:55pm

Kurt Degiorgio

Comments

Sergey Alexandrovich Kryukov 6-Apr-11 14:47pm

Should work, my 5.
--SA

#realJSOP · Answer 2 · 2011-04-06T02:26:00

Solution 4

I would use XML files. Check out this article. I wrote it for C++/MFC, but you should be able to adapt it to Borland C++ easily enough.

XML Application Profile Class[^]

Posted 6-Apr-11 2:26am

#realJSOP

Comments

Sergey Alexandrovich Kryukov 6-Apr-11 14:47pm

Much better choice. My 5.
--SA

CPallini 6-Apr-11 15:31pm

Incidentally, John's proposed article wouldn't work without registry...:-D

Sergey Alexandrovich Kryukov 6-Apr-11 17:54pm

Oh really?! Well, that would certainly makes John's arguments not so convincing, but his idea is good nevertheless. Registry must die (maybe not, but limited to system-wide settings)!

I used to propose a different variant which is fundamentally important to me: Data Contract. (And nothing to do with the Registry, of course. :-) Too bad I cannot reference it here: it's for .NET only.
By the way, in many places of .NET documentation Microsoft officially recommends to give up installation and develop products which are installed by just copy (xcopy or whatever). I understand you're not very interested in references. Me neither; I more rely on my own head.

Thank you.
--SA

#realJSOP 6-Apr-11 18:21pm

See my reply to Henry. The registry use he talks about is because I use a COM DLL provided by Microsoft. I'm not breaking my rule of storing anything in the registry from my own apps.

Sergey Alexandrovich Kryukov 6-Apr-11 19:06pm

Thank you for the explanation. On the principal issue about Registry use I already supported you.
--SA

CPallini 7-Apr-11 3:14am

Sorry, I should have pointed out that. I supposed SA knew about it.

CPallini 7-Apr-11 3:12am

Installation by bare copy looks like an attractive idea.

Sergey Alexandrovich Kryukov 7-Apr-11 3:46am

I like if the most, especially like a user. When I have a closely competing choice I prefer non-installing. I have better personal methods of keeping my application organized, after all.

But I also see (and developed) more realistic variant: not installations, but with uninstallation/cleanup. Why? Some codes contaminate registry (or something else) anyway. When you copy the product is starts working and "installs" itself (but in fact simply leave trace; options, etc.) You used it and eventually want to remove. Just run it as a regular application, hit menu item "remove" -- it cleans all the traces and quits.

It works even with Windows Service. It can be run as application and self install itself as a service. Eventually you want to unregister the service, deleting directory is not enough -- needs the procedure of uninstall. I recently developed such system. Every assembly can implement some special interface for ununstallation. Uninstallation utility just loads all the assemblies without exclusion. If this interface is implemented and manifested through a special assembly attribute (found by Reflection) -- calls unistallation method. Done.

--SA

#realJSOP 6-Apr-11 18:20pm

But it's not because I store anything in it. It's because of the Microsoft COM DLL it uses, and I never said anything about the OS using the registry, I said I don't stored data in it.

Sergey Alexandrovich Kryukov 6-Apr-11 19:07pm

Perfect. It means we're agree on using the Registry.
Thank you for the note.
--SA

CPallini 7-Apr-11 3:09am

Yes, the registry is a one of the fundamental mechanisms supporting COM. I don't store myself generic 'data' inside registry, I use it for (some) applications settings.

CPallini · Answer 3 · 2011-04-05T23:58:00

Solution 2

You may read/write INI files using Windows API functions like WritePrivateProfileString.
You may find such functions listed at the bottom of this MSDN page[^].
As the documentation page remarks:

These functions are provided only for compatibility with 16-bit versions of Windows. New applications should use the registry.

Posted 5-Apr-11 23:58pm

CPallini

Comments

#realJSOP 6-Apr-11 6:04am

Of course, no programmer in his right mind is going to intentionally use the registry. I know I avoid it like the plague.

CPallini 6-Apr-11 6:08am

The registry (tree) structure is much better than the INI files one, in my opinion.

Hans Dietrich 6-Apr-11 6:48am

It seems like this goes in cycles. First, we had INI files. Then that was bad (per MS), we should use the registry. Then with .NET we're told to use config files (aka INI files). I suppose it will be The Cloud next. :)

#realJSOP 6-Apr-11 8:23am

It's never been a cycle for me. Look at what we have right now. Vista/Weven won't even let your write to the registry without the right permissions. This inherently BREAKS pretty much every app that did so in the past. I have never had a reason or seen a justification for general use of the the registry for storing data.

CPallini 6-Apr-11 8:29am

The registry is a central repository for storing application settings (not general data). It has drawbacks, of course, but it also has certain advantages (the tree structure, for instance).

#realJSOP 6-Apr-11 8:45am

I refuse to use it for anything. I treat it like "goto".

Sergey Alexandrovich Kryukov 6-Apr-11 14:45pm

John, you're absolutely right. That was Microsoft's mistake, now admitted my Microsoft people. My thing is: I never followed this mistake, as well as John. My own head is more important to me. I also managed to skip several technologies which have been considered trendy but later gone nowhere. Critical thinking really helps.
--SA

CPallini 6-Apr-11 15:26pm

So, what can I say? John ( and SAK ), please, goto registry! :-D

Sergey Alexandrovich Kryukov 6-Apr-11 14:43pm

John's is right. The cycle is when you blindfolded and follow the trend. This is bad.
Finally, Microsoft people admitted Registry is bad.
The style encouraged by .NET developing shifts things in right direction.
Even xcopy-stype installation is encouraged (best installation type to me).
--SA

CPallini 6-Apr-11 15:29pm

When did Microsoft people admit the registry is bad (not that is of any importance to me)?

Sergey Alexandrovich Kryukov 6-Apr-11 17:46pm

Sorry, I read some article, did not bookmark them. As you're not extremely interested in the proof link, I hope you forgive me.
--SA

CPallini 7-Apr-11 3:06am

Of course I trust you and I'm not going to fight a religious war about the registry. :-)

Sergey Alexandrovich Kryukov 7-Apr-11 3:23am

Thank you.

Kurt Degiorgio 6-Apr-11 7:36am

registry is better but for simple configurations its more worth it to use INI files then the registry

Sergey Alexandrovich Kryukov 6-Apr-11 14:46pm

Simple does not mean better.
Registry is simple being contaminated by too many players. Don't add to it!
--SA