From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: creating unibyte strings
Date: Sun, 24 Mar 2019 22:51:16 +0800 [thread overview]
Message-ID: <CADtN0WK_P1D8NqqoEJKLMT3dsN5Wf=xmsCTEZZX-maC3SN_tQg@mail.gmail.com> (raw)
In-Reply-To: <83sgvfq6yv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
On Fri, 22 Mar 2019 at 23:14, Eli Zaretskii <eliz@gnu.org> wrote:
> Because the number of Emacs features that require you to submit a
> unibyte string is very small.
In the one native module that I have written, integration of GSSAPI, I end
up passing large byte buffers back and forth between Elisp and C. There
really is no efficient way to do this, so I ended up having to use vectors
and use extract_integer in a loop.
Am I misunderstanding this discussion, and there is a better way to pass
binary buffers to modules that I don't know about?
This is what the current code looks like, and it's not really pretty:
https://github.com/lokedhs/emacs-gssapi/blob/master/gssapi.c#L382
Regards,
Elias
[-- Attachment #2: Type: text/html, Size: 1183 bytes --]
next prev parent reply other threads:[~2019-03-24 14:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:12 Oddities with dynamic modules Eli Zaretskii
2018-10-12 14:29 ` Kaushal Modi
2019-02-10 20:23 ` Philipp Stephani
2019-02-11 15:45 ` Eli Zaretskii
2019-02-11 16:04 ` Yuri Khan
2019-03-21 20:04 ` Philipp Stephani
2019-03-21 20:17 ` Eli Zaretskii
2019-03-21 20:32 ` Philipp Stephani
2019-03-21 20:46 ` Eli Zaretskii
2019-03-21 20:51 ` Philipp Stephani
2019-03-21 20:12 ` Philipp Stephani
2019-03-21 20:25 ` Eli Zaretskii
2019-03-21 20:34 ` Philipp Stephani
2019-03-21 20:51 ` Eli Zaretskii
2019-03-21 20:58 ` Philipp Stephani
2019-03-22 1:26 ` creating unibyte strings (was: Oddities with dynamic modules) Stefan Monnier
2019-03-22 7:41 ` Eli Zaretskii
2019-03-22 12:33 ` creating unibyte strings Stefan Monnier
2019-03-22 13:27 ` Eli Zaretskii
2019-03-22 14:23 ` Stefan Monnier
2019-03-22 15:11 ` Eli Zaretskii
2019-03-22 15:37 ` Stefan Monnier
2019-03-22 15:54 ` Eli Zaretskii
2019-03-24 14:51 ` Elias Mårtenson [this message]
2019-03-24 17:10 ` Eli Zaretskii
2019-03-25 1:47 ` Elias Mårtenson
2019-03-25 3:41 ` Eli Zaretskii
2019-03-26 10:23 ` Elias Mårtenson
2019-03-26 11:12 ` Stefan Monnier
2019-03-22 8:20 ` Oddities with dynamic modules 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='CADtN0WK_P1D8NqqoEJKLMT3dsN5Wf=xmsCTEZZX-maC3SN_tQg@mail.gmail.com' \
--to=lokedhs@gmail.com \
--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 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).