lautarox

Which library is used to manipulate the windows registry in c? Is it there any doc about it?
Thanks

bithub

Just use the Win32 registry API.

__________________
bit∙hub [bit-huhb] n. A source and destination for information.

lautarox

But, don't you need a Microsoft Visual environment to use it?

bithub

I think you just need the platform SDK installed.

__________________
bit∙hub [bit-huhb] n. A source and destination for information.

lautarox

Mmm.. I really don't know, I'm not a Windows native programmer, if I have the SDK installed, how can I include the libraries?

idelovski

Biggest problem with Registry API is the naming conventions, the names used for certain entities in the api. Be sure to understand that first. Then the rest will come much easier.

I remember staring at some example code and the documentation and I couldn't connect one with the other. I felt stupid very often while I was dealing with the registry.

Read this post by Raymond Chen and try to read the comments too.

---

I see while I was writing this, you two were talking about some very basic issues. You must have some C compiler for Windows? If you can't link the library to your exe, you can always use LoadLibrary() and GetProcAddress().

bithub

What compiler are you using?

__________________
bit∙hub [bit-huhb] n. A source and destination for information.

lautarox

DJGPP, which one will you recommend me?

bithub

That appears to be a DOS compiler. I suggest you use MS Visual Studio Express which is free.

__________________
bit∙hub [bit-huhb] n. A source and destination for information.

lautarox

Thanks, I'll take a look at it, it's a DOS compiler, but I was thinking to use GTK+ with it.. but well, I think I'll have to use the Visual Studio

Sebastiani

The mingw port of gcc is also an excellent compiler for Windows, plus if you're using C++, it's more standard-compliant than the Microsoft compiler. At any rate, to use the API any Windows compiler will do - just include windows.h.

abachler

If you have to ask that you definitely should not be messing witht eh registry.

__________________
He is free, you say. Ah! That is his misfortune… These men… [have] the most terrible, the most imperious of masters, that is, need. … They must therefore find someone to hire them, or die of hunger. Is that to be free? - Simon Linguet

Elysia

It's fine if storing and retrieving data.

__________________
Using: Microsoft Windows™ 7 Professional (x64), Microsoft Visual Studio™ 2008 Team System
I dedicated my life to helping others. This is only a small sample of what they said:
"Thanks Elysia. You're a programming master! How the hell do you know every thing?"
Quoted... at least once.

abachler

The registry is not a scratch pad to save all your inane application specific data in.

__________________
He is free, you say. Ah! That is his misfortune… These men… [have] the most terrible, the most imperious of masters, that is, need. … They must therefore find someone to hire them, or die of hunger. Is that to be free? - Simon Linguet

Sebastiani

Hmm. Maybe someone should have informed MS about that.

Seriously, though, I don't think Elysia was implying that. The purpose of the registry isn't just to provide a database for the system but in fact all applications. Naturally, there are probably some "common sense" exceptions that should be observed (for the sake of system performance, at least) such as not storing massive amounts of data there (eg: code, output from log files, etc), but using it to store important application settings and the like makes good sense for a number of reasons (more uniform access for your application, the system, other programs, etc, less complex logic for storing/retrieving database-centric data, etc). The main thing though, is just to be consistent, and to be very careful not to accidentally overwrite system-critical data, obviously.