From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: carlo@runaway.xs4all.nl
Cc: egcs@cygnus.com
Subject: Re: #pragma interface && generating virtual tables (of templates?)
Date: Sat, 20 Feb 1999 11:35:00 -0000 [thread overview]
Message-ID: <199902201932.UAA03305@mira.isdn.cs.tu-berlin.de> (raw)
In-Reply-To: < 199902201741.SAA11876@jolan.ppro > (message from Carlo Wood onSat, 20 Feb 1999 18:41:12 +0100 (CET))
> /home/carlo/c++/egcs.bugs/bug3/ircd.lag.cc:34: undefined reference to `server_sock_dct virtual table'
[...]
> Am I correct to think that this would be a bug, because
> templates should not be influenced by '#pragma interface'
> at all (since they don't generate code by themselfs to
> begin with)?
I'd agree this is a bug, at least on the information you provided. Of
course, providing a full bug support (i.e. including preprocessor
output of ircd.lag.ii) shouldn't be that difficult, unless you've
copyright problems.
The virtual table for server_sock_dct should get emitted into
ircd.lag.o. As a work-around, you can probably force this by
implementing get_output_stream out-of-line.
> I understand this is all pretty vague :(, because I can't provide
> a working example - but perhaps someone can give me a clue on
> whether or not using #pragma interface is deprecated in this case
> and/or if I can organize things differently so I won't get undefined
> virtual tables all the time :)
I'd say #pragma interface is deprecated, period. If you count the
trouble you had with it, don't you agree that it wasn't worth it?
With the new weak and link-once symbols on Linux-ELF, there is hardly
any use for it anymore.
Regards,
Martin
WARNING: multiple messages have this Message-ID
From: "Martin v. Loewis" <martin@mira.isdn.cs.tu-berlin.de>
To: carlo@runaway.xs4all.nl
Cc: egcs@cygnus.com
Subject: Re: #pragma interface && generating virtual tables (of templates?)
Date: Sun, 28 Feb 1999 22:53:00 -0000 [thread overview]
Message-ID: <199902201932.UAA03305@mira.isdn.cs.tu-berlin.de> (raw)
Message-ID: <19990228225300.9a3O1gphnuFotrLPR3Yhn4f4r8Kk1OTYh6GvsmTTUI8@z> (raw)
In-Reply-To: <199902201741.SAA11876@jolan.ppro>
> /home/carlo/c++/egcs.bugs/bug3/ircd.lag.cc:34: undefined reference to `server_sock_dct virtual table'
[...]
> Am I correct to think that this would be a bug, because
> templates should not be influenced by '#pragma interface'
> at all (since they don't generate code by themselfs to
> begin with)?
I'd agree this is a bug, at least on the information you provided. Of
course, providing a full bug support (i.e. including preprocessor
output of ircd.lag.ii) shouldn't be that difficult, unless you've
copyright problems.
The virtual table for server_sock_dct should get emitted into
ircd.lag.o. As a work-around, you can probably force this by
implementing get_output_stream out-of-line.
> I understand this is all pretty vague :(, because I can't provide
> a working example - but perhaps someone can give me a clue on
> whether or not using #pragma interface is deprecated in this case
> and/or if I can organize things differently so I won't get undefined
> virtual tables all the time :)
I'd say #pragma interface is deprecated, period. If you count the
trouble you had with it, don't you agree that it wasn't worth it?
With the new weak and link-once symbols on Linux-ELF, there is hardly
any use for it anymore.
Regards,
Martin
next prev parent reply other threads:[~1999-02-20 11:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-20 10:38 Carlo Wood
[not found] ` < 199902201741.SAA11876@jolan.ppro >
1999-02-20 11:35 ` Martin v. Loewis [this message]
[not found] ` < 199902201932.UAA03305@mira.isdn.cs.tu-berlin.de >
1999-02-20 20:38 ` Carlo Wood
1999-02-28 22:53 ` Carlo Wood
1999-02-28 22:53 ` Martin v. Loewis
1999-02-28 22:53 ` Carlo Wood
1999-02-22 13:30 Mike Stump
[not found] ` < 199902222130.NAA00669@kankakee.wrs.com >
1999-02-22 15:52 ` Martin v. Loewis
1999-02-28 22:53 ` Martin v. Loewis
1999-02-28 22:53 ` Mike Stump
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199902201932.UAA03305@mira.isdn.cs.tu-berlin.de \
--to=martin@mira.isdn.cs.tu-berlin.de \
--cc=carlo@runaway.xs4all.nl \
--cc=egcs@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).