From: Mike Gran <spk121@yahoo.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Replace ltdl with GLib's GModule
Date: Wed, 25 Mar 2020 05:41:30 -0700 [thread overview]
Message-ID: <20200325124130.GA2617590@spikycactus.com> (raw)
In-Reply-To: <CACsJy8D4OW6kdW2X+BrYwb_VKxfmuvQzk7n4g0ZLFfnHqModgw@mail.gmail.com>
On Wed, Mar 25, 2020 at 04:33:50PM +0700, Duy Nguyen wrote:
> On Wed, Mar 25, 2020 at 5:24 AM Mike Gran <spk121@yahoo.com> wrote:
> >
> > Hello all-
> >
> > In a fit of pique, I pushed a new branch of Guile to the repo
> > called wip-replace-ltdl-with-gmodule. It replaces the dynamic linking
> > library libltdl from libtool with the analagous library GModule
> > from GLib. It was remarkably easy, and, after a cursory test
> > I was surprised to find that it seems to be working.
> >
> > GModule itself is a standalone library, but, I think it depends
> > on GLib. It might be possible to remove that dependency without
> > much difficulty, but unfortunately, then you would be left with
> > another library to maintain.
> >
> > Anyway, you may find it amusing, at least.
>
> So knee-jerk reaction, what does GModule do better than libltdl? Or
> perhaps why is libltdl "bad"?
Technically, GModule and libltdl are quite similar. But
1. Libtool hasn't made a release in 6 years. For something so
often used in GNU, it seems to be quite neglected.
2. Its default error message "file not found" doesn't always mean
that the file is not found.
I haven't used GModule with Guile enough to decide if it is
technically better, yet. But, it is updated more often.
-Mike Gran
next prev parent reply other threads:[~2020-03-25 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200324222429.GA2587085.ref@spikycactus.com>
2020-03-24 22:24 ` Replace ltdl with GLib's GModule Mike Gran
2020-03-25 9:33 ` Duy Nguyen
2020-03-25 12:41 ` Mike Gran [this message]
2020-03-27 12:01 ` Ludovic Courtès
2020-03-27 13:27 ` Eli Zaretskii
2020-03-27 17:03 ` Mike Gran
2020-03-25 12:11 dsmich
-- strict thread matches above, loose matches on Subject: below --
2020-03-25 14:58 dsmich
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200325124130.GA2617590@spikycactus.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=pclouds@gmail.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).