From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Dynamic modules: emacs-module.c and signaling errors
Date: Thu, 26 Nov 2015 13:20:46 -0800 [thread overview]
Message-ID: <565777AE.6030204@cs.ucla.edu> (raw)
In-Reply-To: <83poywtsxl.fsf@gnu.org>
Eli Zaretskii wrote:
> It's not obvious to me, sorry. The costs of the current code are
> minimal, and the advantages to have the "raw" functionality in
> addition to what we have aren't clear-cut.
My admittedly vague impression is that Stefan's approach would be friendlier to
module authors who want to write code that feels like Emacs's current C code.
This should be a plus, no?
I don't fully understand why the current emacs-module.c is as complicated as it
is, to be honest. I know it has something to do with C++ exception handling,
but the details still escape me. But really, we should support C modules well
too, as C is still the lingua franca for low-level software integration. And
"well" does not mean "every time you call a function you then have to call some
other function to see whether the first function worked".
next prev parent reply other threads:[~2015-11-26 21:20 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 19:41 Dynamic modules: emacs-module.c and signaling errors Eli Zaretskii
2015-11-24 19:45 ` Eli Zaretskii
2015-11-24 20:12 ` Tom Tromey
2015-11-24 20:49 ` Eli Zaretskii
2015-11-24 21:34 ` Paul Eggert
2015-11-24 21:55 ` Daniel Colascione
2015-11-25 6:52 ` Paul Eggert
2015-11-25 7:03 ` Daniel Colascione
2015-11-25 7:14 ` Paul Eggert
2015-11-25 7:18 ` Daniel Colascione
2015-11-25 7:23 ` Paul Eggert
2015-11-25 7:25 ` Daniel Colascione
2015-11-25 7:49 ` Paul Eggert
2015-11-25 7:52 ` Daniel Colascione
2015-11-25 7:58 ` Paul Eggert
2015-11-25 8:12 ` Daniel Colascione
2015-11-25 8:24 ` Paul Eggert
2015-11-25 8:50 ` Daniel Colascione
2015-11-25 9:11 ` Daniel Colascione
2015-11-25 18:19 ` Eli Zaretskii
2015-11-25 18:26 ` Philipp Stephani
2015-11-25 19:19 ` Eli Zaretskii
2015-11-25 21:52 ` Philipp Stephani
2015-11-25 17:34 ` Paul Eggert
2015-11-24 22:21 ` Tom Tromey
2015-11-25 6:55 ` Paul Eggert
2015-11-25 17:30 ` Eli Zaretskii
2015-11-25 17:34 ` Paul Eggert
2015-11-25 21:23 ` Stefan Monnier
2015-11-26 15:42 ` Eli Zaretskii
2015-11-26 16:36 ` Stefan Monnier
2015-11-26 17:08 ` Eli Zaretskii
2015-11-26 19:28 ` Stefan Monnier
2015-11-26 19:34 ` Eli Zaretskii
2015-11-26 20:11 ` Stefan Monnier
2015-11-26 20:19 ` Eli Zaretskii
2015-11-26 21:20 ` Paul Eggert [this message]
2015-11-26 22:29 ` Philipp Stephani
2015-11-26 22:33 ` Philipp Stephani
2015-11-27 1:06 ` Stefan Monnier
2015-11-27 1:10 ` Daniel Colascione
2015-11-27 15:06 ` Stefan Monnier
2015-11-27 8:12 ` Eli Zaretskii
2015-11-27 9:11 ` Eli Zaretskii
2015-11-27 12:25 ` Aurélien Aptel
2015-11-27 14:44 ` Eli Zaretskii
2015-11-28 23:31 ` Paul Eggert
2015-11-27 1:21 ` Stefan Monnier
2015-11-27 8:26 ` Eli Zaretskii
2015-11-27 15:15 ` Stefan Monnier
2015-11-27 15:57 ` Eli Zaretskii
2015-11-27 16:29 ` Stefan Monnier
2015-11-27 17:38 ` Eli Zaretskii
2015-11-27 17:54 ` Stefan Monnier
2015-11-25 18:10 ` Tom Tromey
2015-11-25 18:15 ` Eli Zaretskii
2015-11-25 18:09 ` Philipp Stephani
2015-11-25 21:19 ` Stefan Monnier
2015-11-26 15:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=565777AE.6030204@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.