From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: hi@yagnesh.org, 19346@debbugs.gnu.org, larsi@gnus.org
Subject: bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p
Date: Fri, 12 Dec 2014 16:54:39 +0200 [thread overview]
Message-ID: <837fxwsyts.fsf@gnu.org> (raw)
In-Reply-To: <jwv61dhvsn4.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: hi@yagnesh.org, 19346@debbugs.gnu.org, larsi@gnus.org
> Date: Fri, 12 Dec 2014 09:40:44 -0500
>
> > Does that mean a module can ever provide only one monolith feature?
>
> That's how Elisp modules work, and it hasn't been a serious problem so
> far, has it?
ELisp modules are much simpler than dynamic modules written in some
compiled language. Look at GnuTLS: it can be compiled with umpteen
different optional features. If we now force each module to provide
just one feature, you'd need lots of different 'gnutls-FOO' symbols,
for all the combinations of the options. That doesn't sound very
elegant to me, especially since the savings are just one API which
could have solved the same problem more cleanly.
next prev parent reply other threads:[~2014-12-12 14:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 10:57 bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p Yagnesh Raghava Yakkala
2014-12-11 15:57 ` Lars Magne Ingebrigtsen
2014-12-11 16:08 ` Ted Zlatanov
2014-12-11 16:16 ` Lars Magne Ingebrigtsen
2014-12-11 18:00 ` Eli Zaretskii
2014-12-11 19:16 ` Stefan Monnier
2014-12-11 19:48 ` Ted Zlatanov
2014-12-11 21:03 ` Eli Zaretskii
2014-12-11 22:58 ` Ted Zlatanov
2014-12-12 0:02 ` Stefan Monnier
2014-12-12 0:21 ` Ted Zlatanov
2014-12-12 1:33 ` Stefan Monnier
2014-12-12 7:58 ` Eli Zaretskii
2014-12-12 14:40 ` Stefan Monnier
2014-12-12 14:54 ` Eli Zaretskii [this message]
2014-12-12 16:39 ` Stefan Monnier
2014-12-12 19:04 ` Eli Zaretskii
2014-12-12 21:56 ` Stefan Monnier
2014-12-13 7:43 ` Eli Zaretskii
2014-12-13 14:21 ` Stefan Monnier
2014-12-13 15:20 ` Eli Zaretskii
2014-12-12 13:19 ` Ted Zlatanov
2014-12-12 14:47 ` Stefan Monnier
2014-12-12 7:49 ` Eli Zaretskii
2014-12-12 14:42 ` Stefan Monnier
2014-12-12 14:55 ` Eli Zaretskii
2014-12-12 16:33 ` Stefan Monnier
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837fxwsyts.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19346@debbugs.gnu.org \
--cc=hi@yagnesh.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).