Printable View
Hi Paul,
Shall do so in the future. Actaully when I reomved the initialization from the class scope everything worked fine. I also think that the code does not account completely for multiple inclusions.
I am not sure whether #ifndef is better or #pragma once is better.
Thanks for highlighting that. :thumb:Quote:
Originally Posted by Paul McKenzie
somebody please help me on the first problem.
The warning states that you have functions implemented more than once. Your job is to look at the function(s) the linker is complaining about and see where they are defined and implemented in your project.
Are theses implemented in two (or more) source modules?
Regards,
Paul McKenzie
Quote:
Originally Posted by Paul McKenzie
Hi Paul,
I plan to do so. They are implemented in one source only.
The Saint,
I don't have much time to follow all of the opsts in your thread ...
but personally i am sure limiting the resource used as small as possible is always highly recommended, although that would bring about performance issues...that is why the target should be at how to set up an equillibrium equation to gain most benifits in a certain application under a given situation..
If it isn't implemeted in two or more source modules, then you are linking in two or more object modules that contain the implementations. If you have an a.obj or a.lib, and you have a b.obj or b.lib, and for some reason a function is found in two or more of these libraries, the linker will warn you.
Therefore a search for a function in the source code being implemented more than once may not find what you're looking for. Look at your project, look what is being linked. The linker *is* finding two implementations in the object code/libraries being linked.
Regards,
Paul McKenzie