unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Syohei Yoshida <syohex@gmail.com>,
	Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: good examples of Emacs modules?
Date: Tue, 03 May 2016 20:48:49 +0000	[thread overview]
Message-ID: <CAArVCkTtHSE56uDR2Kbujvuq=bO_BVuMrizGsuoH2m=nC12hLg@mail.gmail.com> (raw)
In-Reply-To: <CAFX6MOOOT4ghjuC5uLjfY7yfs+0q2WaBO7wwROuWqTqOyWs94Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Syohei Yoshida <syohex@gmail.com> schrieb am Sa., 2. Apr. 2016 um 04:10 Uhr:

> Hi,
>
> >
> > Syohei, I really like what you did and I would be interested in your
> > feedback on what could be improved, what should we add&optimize in the
> > module API, etc.
> >
>
> I want vector(or list) and hash table API(there are some vector API in
> emacs_env).
> I know that we can use them via env->funcall, however we need a lot of
> code for
> using them(intern function name, set arguments to emacs_value array,
> env->funcall).
> I think it is useful if we can handle vector, list, hash table easily.
>

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.

[-- Attachment #2: Type: text/html, Size: 1397 bytes --]

  reply	other threads:[~2016-05-03 20:48 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 [this message]
2016-05-03 22:16                   ` Stefan Monnier
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

  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='CAArVCkTtHSE56uDR2Kbujvuq=bO_BVuMrizGsuoH2m=nC12hLg@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=syohex@gmail.com \
    /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).