|
do you want us to write the code for you ?
or you're stuck on a particular point ?
please ask a specific question !
|
|
|
|
|
it depends on what you want to do, to clean. 
to access to the registry there are many functions in the form Reg****Key, as RegOpenKeyEx, RegCloseKey, RegDeleteKey, RegSetValueEx, ...
Russell
|
|
|
|
|
Write to me. I accept paypal.
Nobody can give you wiser advice than yourself. - Cicero
.·´¯`·->ßRÅhmmÃ<-·´¯`·.
|
|
|
|
|
brahmma wrote: Write to me. I accept paypal
classic...
me accept payment in kind (if his GF is correct enough) :->
|
|
|
|
|
I'm imagining you in a dark street, holding up a sign...
"Will code for nookie!"
Iain.
|
|
|
|
|
I am currently working on an asset register as a project and would like to acquire information on the hardware as well as software installed on a host
Can anyone help!!
Kim
|
|
|
|
|
kim007 wrote: I am currently working on an asset register as a project and would like to acquire information on the hardware as well as software installed on a host
Sounds fun. Good luck.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
|
Hello,
I have a major problem with the .h header files.
The Compiler (VS2003) does not seem to care about my function definition in the header file if implemented in another .cpp file.
Here is an example:
[myfunc.h]
#pragma once
int DLLInit(char* DLLInfo);
[myfunc.cpp]
#include "myfunc.h"
int DLLInit(int DLLInfoInt)
{
return 0;
}
I seem to be missing the whole point of a header file if the compiler does not detect the false declaration of variable name and type.... 
I want to include the header file in the project using the dll, too, so it is important to check parameter and type of function parameters, etc.
Maybe this is a very simple problem but I can't find a solution yet..
Any help?
thx in advance
|
|
|
|
|
sGrabert wrote: [myfunc.h]
#pragma once
int DLLInit(char* DLLInfo);
[myfunc.cpp]
#include "myfunc.h"
int DLLInit(int DLLInfoInt)
{
return 0;
}
check your code once again...
you declare a function that gets a char*, but you define a function that gets an int...
why the compiler wouldn't complain then ? 
|
|
|
|
|
sGrabert wrote: I seem to be missing the whole point of a header file if the compiler does not detect the false declaration of variable name and type....
Why would it ? Function overloading is possible in C++ and you don't need to have a declaration for your functions. So, in your case you have a declaration of a function but no body for this function. As long as you don't call that function, everything will be fine. But once you call that function, you'll get a linker error.
So, actually, what is your real problem ? I don't understand what you are trying to achieve...
|
|
|
|
|
Cedric Moonen wrote: you have a declaration of a function but no body for this function. As long as you don't call that function, everything will be fine.
that's not true anymore under VS2005 AFAIK (but didn't tested actually)...
|
|
|
|
|
toxcct wrote: that's not true anymore under VS2005 AFAIK (but didn't tested actually)...
I never heard of that and I hardly imagine that...
Suppose that you have three files:
- One main.cpp that contains the main function
- One header file (file.h) that contains a function declaration
- One cpp file (file.cpp) that contains the function definition (of the previous function).
Suppose that you call this function in the main function. How can the compiler know, when compiling main.cpp that this function is actually defined in file.cpp ? What if you didn't include file.cpp in your project ?
Thus the error is generated at link time, when the linker cannot find the compiled function in the object files.
|
|
|
|
|
hum, actually, i was more saying that the compiler (or maybe the linker in fact) will throw a warning if you declare a function (in a .h mostly) that is never defined...
|
|
|
|
|
hum, actually, i was more saying that the compiler (or maybe the linker in fact) will throw a warning if you declare a function (in a .h mostly) that is never defined...
This is a helpfull warning indeed  , VS2003 fails to warn you about this.
|
|
|
|
|
No warning/error there either 
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
toxcct wrote: that's not true anymore under VS2005 AFAIK
It's still true 
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
|
Why would it ? Function overloading is possible in C++ and you don't need to have a declaration for your functions. So, in your case you have a declaration of a function but no body for this function. As long as you don't call that function, everything will be fine. But once you call that function, you'll get a linker error.
Okay, I called the function and finally  got a linker error, I was expecting an error during compiling...
I developed using Delphi the last 5 years and the ambigious overloading of types/variables/function C++ without any visible effect is driving me crazy...
In Delphi you had to add OVERLOAD or use a typecast..
The main reason for this problem:
- i want to create a dll that can be called from another app, using dynamic linking
- works so far
- I changed the implementation of a function (by accident) and got a very confusing exception after calling the function from the dll but no compiler error, though i linked the header file from the dll.
|
|
|
|
|
sGrabert wrote: - I changed the implementation of a function (by accident) and got a very confusing exception after calling the function from the dll but no compiler error, though i linked the header file from the dll.
What did you change exactly ? Because if the linker doesn't find an implementation for the function, it will show you a link error.
|
|
|
|
|
(i renamed the caption to "minor", seems more appropriate)
workflow:
1. DLL
1a. creating the dll.h file with function prototypes
1b. creating the dll.cpp file with function implementation
(the dll itself does not use the functions, so no linking check here!)
2. app
2a. dynamic loading of dll using dll.h
I wanted to ensure the correct calling of functions in the app using the .h file:
(i have cut all the class stuff etc.)
<br />
[dll.h]<br />
int DLLInit(char* DLLInfo);<br />
<br />
[app.h]<br />
#include "dll.h"<br />
typedef bool (*DLLINIT)(char* DLLInfo);<br />
DLLINIT pDLLInit;<br />
<br />
pDLLInit= (DLLINIT)::GetProcAddress(m_DLL, "DLLInit");<br />
Is this possible (or even useful) in any way?
-- modified at 5:50 Thursday 23rd August, 2007
|
|
|
|
|
Hello,
i like to know is it posible to include one application into other one?
I hava a dialogapplication with tabs, in one tab i like to include a external application,
is that posible, so that this extern app. run in my tab control? :->
thanks in advance
termal
|
|
|
|
|
Only if that external application is expecting to be hosted, and you call it with (eg):
c:\myotherapp.exe /hwndparent:0x0046747
This is pretty much how screen savers work, and how they are shown in the screen saver preview window.
OK, not *completely* true - you could try using hooks, detecting any window creation of the child exe, and try changing the window parameters to WS_CHILD - but that's a lot of work, and still not guaranteed to work.
Iain.
|
|
|
|
|
Hello,
thanks for your idea!
regards
termal
|
|
|
|
|
This was the concept behind COM servers. An ActiveX control is basically a mini application that runs in the context of a host.
"A good athlete is the result of a good and worthy opponent." - David Crow
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
