[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Oddities with dynamic modules

From: Philipp Stephani
Subject: Re: Oddities with dynamic modules
Date: Thu, 21 Mar 2019 21:04:07 +0100

Am Mo., 11. Feb. 2019 um 17:04 Uhr schrieb Yuri Khan <address@hidden>:
> On Mon, Feb 11, 2019 at 10:46 PM Eli Zaretskii <address@hidden> wrote:
> > > 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.
> > IME, inconvenient interfaces are the main reason for them being
> > unstable, but that's me.
> A good middle ground is a minimalistic (but sufficient) API at the
> host side, plus idiomatic convenience wrapper libraries for each
> client language. (The latter need not be maintained by the host API
> maintainer.)

Yes, that's exactly what Daniel suggested in his initial design. It's
also what largely seems to be happening: people have written idiomatic
wrappers for Rust, Go, and probably other languages. Thus I'd say this
is working as inteded.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]