Mail Archives: djgpp/1998/11/30/06:16:53
In article <Pine DOT SUN DOT 3 DOT 91 DOT 981129175153 DOT 4131C-100000 AT is>, djgpp AT delorie DOT com wrote:
>
>On Fri, 27 Nov 1998, Manni Heumann wrote:
>
>> Is DJGPP forgetting functions that were supposed to be inlined, but weren't
>> because of the missing commandline option?
>
>DJGPP isn't forgetting anything. The problem is that the C++ class
>library doesn't include a stand-alone version of these functions, only an
>inline version in the header.
>
>I'm not sure whether this is a bug, but if it is, it should be reported
>to the appropriate GNU news group, since that's where libgpp comes form.
Don't get me wrong, I'm not complaining (there is nothing to complain about),
I'm just trying to understand what is going on here:
So, the functions are defined and declared in the header-file, which is a
proposal to the compiler to inline them.
Running the compiler without the commandline switches necessary for inlining,
the compiler, of course, will not do the inlining.
What now? In any case the functions should have been compiled. And, inlined or
not, they should be available in the file where I included the header.
Then why doesn't the linker see them right there?
The only answer I find is that the compiler drops them, because it cannot
inline them.
Why? Even if I use the right switches and request an inline and won't get and
inlined version in any case. Instead I get a warning message and a function
that is linked in my program.
Short: I don't get it.
Bye,
-----------------------------------------------------------
Manni Heumann
Bielefeld, Germany
Spammers use reply-adress,
all others: mheumann AT post DOT uni-bielefeld DOT de
-----------------------------------------------------------
- Raw text -