From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: good examples of Emacs modules?
Date: Tue, 03 May 2016 18:16:12 -0400 [thread overview]
Message-ID: <jwv1t5ig57h.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CAArVCkTtHSE56uDR2Kbujvuq=bO_BVuMrizGsuoH2m=nC12hLg@mail.gmail.com
> I think the API should be kept as small as possible. Every environment
> member has to be designed, maintained, etc. If we add vector, list, and
> hash table functions, why stop there? Why not add buffer and string
> functions? Or process and network functions? I think new functions should
> only be added if they either solve a problem that could not be solved
> otherwise, or the replacement code would be very awkward, or there is a
> proven significant efficiency gain.
FWIW, I completely agree with keeping the API minimalist. I think we
can accommodate the request "on the other side", e.g. with a library (or
several of them) that the module can link with (probably statically)
which will do the dance of interning the function name and such.
Stefan
next prev parent reply other threads:[~2016-05-03 22:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 23:17 good examples of Emacs modules? Paul Eggert
2016-03-31 14:49 ` Aurélien Aptel
2016-03-31 15:34 ` Óscar Fuentes
2016-03-31 16:53 ` Eli Zaretskii
2016-03-31 17:07 ` Óscar Fuentes
2016-03-31 17:39 ` Eli Zaretskii
2016-03-31 20:23 ` Óscar Fuentes
2016-03-31 21:29 ` Aurélien Aptel
2016-03-31 21:59 ` Óscar Fuentes
2016-04-01 7:18 ` Eli Zaretskii
2016-04-01 13:20 ` Óscar Fuentes
2016-04-01 14:02 ` Eli Zaretskii
2016-04-02 2:10 ` Syohei Yoshida
2016-05-03 20:48 ` Philipp Stephani
2016-05-03 22:16 ` Stefan Monnier [this message]
2016-04-01 6:23 ` Eli Zaretskii
2016-04-01 13:25 ` Óscar Fuentes
2016-04-01 14:07 ` Eli Zaretskii
2016-05-03 20:54 ` Philipp Stephani
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=jwv1t5ig57h.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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.