Subject: Re: bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p

From: Eli Zaretskii <[email-masked]>
Date: Fri, 12 Dec 2014 16:54:39 +0200

> From: Stefan Monnier <[email-masked]>
> Cc: [email-masked],  [email-masked],  [email-masked]
> 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.