unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>,
	"Aurélien Aptel" <aurelien.aptel@gmail.com>
Subject: Re: [modules] Possible return values of the env->type_of?
Date: Tue, 25 Dec 2018 17:13:19 +0100	[thread overview]
Message-ID: <CAArVCkTPffo9wSFAqGtb7LDjxxRu2+e1fdp37+wPc9jfQhS-oQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY0oOruiY3ACNZ9F+BFR3jVR3VeNn7bW8_f0CyM29B_p2Q@mail.gmail.com>

Am Fr., 22. Juni 2018 um 19:52 Uhr schrieb Kaushal Modi
<kaushal.modi@gmail.com>:
>
>> Perhaps you'll find Philip's doc useful:
>> https://phst.github.io/emacs-modules#type_of
>
>
> Yes! That's where I figured out the relationship between env->type_of and  type-of.
>
> @Philipp Can that documentation be made part of the Emacs Manual?

Eli has now written a manual section about modules, which should
contain similar information.

> It's really useful for folks like me who don't know C. In your doc, you say:
>
> > Because the module API is a C API, you have to be familiar with C to write Emacs modules.
>
> But that doesn't seem to be the case for me :) Nim provides enough abstraction to use this API and make the code readable just like Python. This is what I am working on[1].
>
> [1]: https://github.com/kaushalmodi/nim-emacs-module/blob/test-whole-emacs-module/test/modtest.nim

That's great! What I mean is "you have to know enough about syntax and
semantics of C to use the module API correctly", not "you have to know
every detail of C". In particular, the lifetime and threading issues
are quite subtle.



  parent reply	other threads:[~2018-12-25 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 14:41 [modules] Possible return values of the env->type_of? Kaushal Modi
2018-06-22 17:10 ` Kaushal Modi
2018-06-22 17:38 ` Aurélien Aptel
2018-06-22 17:52   ` Kaushal Modi
2018-06-22 18:16     ` Eli Zaretskii
2018-12-25 16:13     ` Philipp Stephani [this message]
2018-06-22 20:58   ` Drew Adams
2018-06-22 18:10 ` Eli Zaretskii

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=CAArVCkTPffo9wSFAqGtb7LDjxxRu2+e1fdp37+wPc9jfQhS-oQ@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=aurelien.aptel@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=kaushal.modi@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.
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).