Re: Oddities with dynamic modules

[Philipp Stephani]

Am Mo., 11. Feb. 2019 um 16:46 Uhr schrieb Eli Zaretskii <address@hidden>:
>
> > From: Philipp Stephani <address@hidden>
> > Date: Sun, 10 Feb 2019 21:23:18 +0100
> > Cc: Emacs developers <address@hidden>
> >
> > >  . Using 'funcall' is unnecessarily cumbersome, because the function
> > >    to be called is passed as an 'emacs_value'.  Why don't we have a
> > >    variant that just accepts a name of a Lisp-callable function as a C
> > >    string?
> >
> > Convenience is not a design goal of the module API. The primary design
> > goals are robustness, stability, simplicity, and minimalism.
>
> I thought simplicity and convenience of use tramps simplicity of the
> implementation, so it is strange to read arguments to the contrary.

Simplicity tends to be the opposite of convenience. Interface
simplicity definitely trumps convenience and implementation
simplicity.

>
> > >  . Why does 'intern' only handle pure ASCII symbol names?  It's not
> > >    like supporting non-ASCII names is hard.
> >
> > Unfortunately it is, due to Emacs underspecifying encoding. If we can
> > manage to write an 'intern' function that accepts UTF-8 strings and
> > only UTF-8 strings, I'm all for it.
>
> What are the problems you have in mind?  After all, this is already
> possible by means of 2 more function calls, as the example in the
> manual shows.  Are there any problems to do the same under the hood,
> instead of requiring users to do that explicitly in their module code?

If users want to have a truly generic "intern" function, they need to
do some legwork anyway because the signature of the "intern"
environment function doesn't allow embedded null bytes. It's also
unclear how non-Unicode symbols should be represented (if at all).
Given that almost all uses of "intern" will use ASCII symbols, it's
fine to restrict the API in this way. I've provided an example for a
wrapper function that allows at least interning of arbitrary Unicode
strings: https://phst.eu/emacs-modules#intern.

>
> > >  . I could understand why equality predicates are not provided in the
> > >    API, but I don't understand why we do provide 'eq' there.  Is it
> > >    that much more important than the other predicates?
> >
> > Yes, it represents a fundamental property of objects.
>
> How is that relevant?  Equality predicates are used very frequently
> when dealing with Lisp objects; 'eq' is not different from others in
> that respect.

I don't recollect the reasoning, but Daniel stated that "eq" is
strictly necessary, so you might want to ask him.

>
> > > IOW, if the API was supposed to be minimal, it looks like it isn't;
> > > and if it wasn't supposed to be minimal, then some important/popular
> > > functions are strangely missing, for reasons I couldn't wrap my head
> > > around.
> >
> > It is *mostly* minimal. A *completely* minimal API would not even have
> > integer and floating-point conversion functions, as those can be
> > written using the string functions. But that would be far less simple
> > and robust.
> > "eq" and "is_not_nil" are special in that they implement access to
> > fundamental object properties and can't fail, so they are fundamental
> > enough to deserve an entry in the module table.
>
> I cannot follow this reasoning, sorry.  It sounds like you are saying
> that the decision what to implement and what not justifies itself
> because it's there.  All I can say is that as someone who wrote a
> couple of lines of code in Emacs, the stuff that is in the API and the
> omissions look quite arbitrary to me.

Please see Daniel's original reasoning for the design. I'm not
claiming perfection for the module API, but it definitely strikes a
very good balance between minimalism and robustness.

>
> > The best source to answer the "why" questions is still the original
> > design document:
> > https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00960.html
>
> Which part(s) of that long document answer these questions, please?

Mostly the first sentence "We want an ABI powerful enough to let C
modules interact with Emacs, but decoupled enough to let the Emacs
core evolve independently."