public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Todd Vierling <tv@pobox.com>
To: egcs@cygnus.com
Subject: exceptions and RTTI and mixed code
Date: Fri, 03 Apr 1998 21:52:00 -0000	[thread overview]
Message-ID: <Pine.NEB.3.96.980402181919.2743D-100000@like.duh.org> (raw)

I'm not sure this has been asked.  I'm unofficially helping integrate egcs
into NetBSD, and I'd like to know if gcc 2.8/egcs can handle mixing code
with exceptions and RTTI (as by default) and code without it can be mixed.
The libstdc++ is built as a shared library, so it obviously can only be one
or the other, not both.  So, if it has RTTI and exceptions compiled in, can
user code be linked to it without using RTTI and exceptions?

-- 
-- Todd Vierling (Personal tv@pobox.com; Bus. todd_vierling@xn.xerox.com)


             reply	other threads:[~1998-04-03 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-03 21:52 Todd Vierling [this message]
1998-04-04 20:05 ` Joe Buck

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=Pine.NEB.3.96.980402181919.2743D-100000@like.duh.org \
    --to=tv@pobox.com \
    --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).