Re: dllexport template function: char* parameter problem
Fabian wrote:
"Ulrich Eckhardt" wrote:
Why do you insist on having all instantiations in the DLL? Why not simply
put the non-template parts into the DLL and make the rest inline?
I'm sure you would have built up the whole project differently. But what I
now have is 6 dlls one of which provides/exports common stuff for the
others and the exe. I'm not sure whether I understand your suggestion
correctly: Wouldn't this in my case mean to have the code for the
non-template parts 5 times (i.e. in each comsumer dll plus the exe)?
I'm not sure I understand you correctly. If you have code in a DLL, it can
be loaded into the same process several times (e.g. by the executable and
other DLLs) without causing additional overhead.
About the parts that are inline, those are actually compiled into each DLL
and executable that uses them, so there they are actually duplicated.
In my philosophy every extra line of code is a potential location of a
bug...
...which is a philosophy I share! However, in this case you don't have extra
code but only the same code (or, due to the use of templates, similar code)
that is only compiled multiple times.
It somehow depends on what you want to achieve. If your goal is only that no
code (written or compiled) is duplicated, you will actually have to go the
way you're trying right now, i.e. to put everything into the DLL. However,
then you will also have code in there that might never be used, e.g. if you
export a function that logs double values but you only use float. My
approach is mostly that I pick the one that is easiest to do (export common
stuff from the DLL, leave templates inline) so I have more time for the
really pressing issues, but that's just my opinion.
I hope I helped more than caused confusion. ;^)
Uli
--
C++ FAQ: http://parashift.com/c++-faq-lite
Sator Laser GmbH
Gesch??ftsf??hrer: Michael W??hrmann, Amtsgericht Hamburg HR B62 932