public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: Re: merged-libs-branch
Date: Tue, 30 Sep 2003 15:41:00 -0000	[thread overview]
Message-ID: <20030930154141.GE3407@redhat.com> (raw)
In-Reply-To: <1064935327.3257.97.camel@escape>

Anthony Green wrote:
> On Tue, 2003-09-30 at 04:04, Gary Benson wrote:
> > It all seems to work beautifully.  Anyone mind if I merge the changes
> > into HEAD?
> 
> Sounds good to me.
> 
> BTW - why isn't this kind of cross linking recommended?

From Uli:
- the order in which the DSO constructors are called might be wrong.
- it may not be possible to unload such a library.
- even if it is, the destructors will not be run at dlclose() time.

Gary

  reply	other threads:[~2003-09-30 15:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 11:04 merged-libs-branch Gary Benson
2003-09-30 15:22 ` merged-libs-branch Anthony Green
2003-09-30 15:41   ` Gary Benson [this message]
2003-10-01 21:39 ` merged-libs-branch Tom Tromey
2003-10-02  8:42   ` merged-libs-branch Gary Benson

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=20030930154141.GE3407@redhat.com \
    --to=gbenson@redhat.com \
    --cc=rhug-rhats@sources.redhat.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).