From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: good examples of Emacs modules?
Date: Thu, 31 Mar 2016 23:59:36 +0200 [thread overview]
Message-ID: <87poua5mwn.fsf@wanadoo.es> (raw)
In-Reply-To: CA+5B0FMs08XnqRLvFD+EzAMohoDYxffXLE92bwwD4=EmesFJCA@mail.gmail.com
Aurélien Aptel <aurelien.aptel+emacs@gmail.com> writes:
> Hi all,
>
> On Thu, Mar 31, 2016 at 10:23 PM, Óscar Fuentes <ofv@wanadoo.es> wrote:
>> consequences.) How objects created by the module system interact with
>> garbage collection is an start.
>
> Every emacs_value allocated inside a Lisp-exposed function becomes
> invalid when control of the function ends (when it exits) unless you
> return that value or you mark it global with the the
> env->make_global_ref() API call.
Ok.
> As I was googling for a browseable emacs git repo to look quickly at
> emacs-module.h I've noticed that Syohei Yoshida (cc'ed) has figured a
> lot of things out by himself (kudos to you!) and has already made some
> simple and not-so-simple modules:
Thank you. The more examples, the better.
I'll like to encourage you to keep expanding the introduction, though.
The type on information it contains saves a lot of head scratching.
BTW, it is necessary to explicitly export the symbols on Windows (and on
GNU/Linux too depending on the arguments used):
int plugin_is_GPL_compatible;
should be
int __declspec(dllexport) plugin_is_GPL_compatible;
(Windows)
int __attribute__ ((visibility("default"))) plugin_is_GPL_compatible;
(GNU/Linux, when you compile your module with -fvisibility=hidden, which
is a Good Thing.)
This is usually implemented with a macro.
More info:
https://gcc.gnu.org/wiki/Visibility
That page mentions C++ but it applies to C too.
[snip]
next prev parent reply other threads:[~2016-03-31 21:59 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 [this message]
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
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=87poua5mwn.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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.