From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mvoteiza@udel.edu, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 5d4c539: Add lcms2 interface
Date: Wed, 13 Sep 2017 12:23:34 -0400 [thread overview]
Message-ID: <jwv60cm3747.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <83mv5yoae0.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 13 Sep 2017 19:01:43 +0300")
>> > configure.ac: Add boilerplate for configuring and detecting liblcms2.
>> Can't this be a module?
> Only if we don't want this functionality in Emacs where the library is
> available.
Hmm... indeed I now see that liblcms2 is already linked into Emacs if we
use the Gtk GUI. It's not linked if you use the Lucid GUI, OTOH.
> To me, modules are for users to extend Emacs, not for us to add
> functionality.
That's one of the benefits. The other is that you don't need to choose
at compile-time which libraries will be (and have to be) available at
run-time.
In Windows, we already do dynamic-loading of libraries such as gnutls,
so the issue is less serious, but in GNU/Linux it's always a hassle.
> It makes very little sense to have anything that is in
> core via modules. I see only disadvantages there: the code is much
> less readable, and has more limitations on what it can do.
That calls for improving the module system, not circumventing it.
Stefan
next prev parent reply other threads:[~2017-09-13 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170913143143.30953.94864@vcs0.savannah.gnu.org>
[not found] ` <20170913143145.6483C2068F@vcs0.savannah.gnu.org>
[not found] ` <jwvmv5y38nt.fsf-monnier+emacsdiffs@gnu.org>
2017-09-13 16:01 ` [Emacs-diffs] master 5d4c539: Add lcms2 interface Eli Zaretskii
2017-09-13 16:23 ` Stefan Monnier [this message]
2017-09-13 17:07 ` Paul Eggert
2017-09-13 17:44 ` Stefan Monnier
2017-09-13 19:24 ` Eli Zaretskii
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=jwv60cm3747.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.