"Kelly Mandrake" <[EMAIL PROTECTED]> writes:
> Ive noticed that I can leave out includes such as iostream and my
> program will still compile.
This is because some *other* header that you do #include already
includes iostream.
> It seems g++ is auto includeing headers,
It doesn't.
> could this
[EMAIL PROTECTED] writes:
> I had not come across that need to have "template<>" in there. Where do
> you say I need to put that?
Exactly where I put it. Correct syntax is:
template <>
inline Units<0,0,0,0,0>::operator double() const
{
return d_val;
}
Without the 'templa
Hi Paul, thanks for that reply there.
I had not come across that need to have "template<>" in there. Where do
you say I need to put that?
Also, I have been able to get those linker errors but I want to somehow
get more information about the location of the attempted cast to
double. Ideally this s
Paul Schneider wrote:
> Guy Harrison wrote:
[snip]
>> "Dynamic allocation" is still the stock answer. Consider also grabbing
>> some older books which cover "batch processing". Most processing is
>> boring repetitive stuff. Half the battle with programming is losing
>> conventional thought. Spars
Ive noticed that I can leave out includes such as iostream and my
program will still compile. It seems g++ is auto includeing headers,
could this be true and if so how might I turn it off.
I had searched google and groups but was unable to find anything
problably because of the search terms I was
[EMAIL PROTECTED] (John Pye) writes:
> // only defined for unitless types
template <> // missing, required:
// units.h:104: error: explicit specialization of
// `Units<0, 0, 0, 0, 0>::operator double() const' must be
introduced by `template <>'
> inlin
Fixed!
The problem was that I was including the header that defines
"PetscInitialize" as extern "C" {}. However, the header was C++ and
the PetscInitialize was overloaded. Thus the dynamic loader was
looking for a C-style PetscInitialize which it could not find as there
were only mangled, C++-st
Hi,
I have a very strange runtime symbol look-up error. While I suppose
this may be slightly off topic, I'm not sure of a more relevent
newsgroup, and I trust the people here have delt with most every
linking problem possible.
I have a c++ shared library that is having problems looking up a symb
