From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: Some dynamic module questions
Date: Fri, 27 Nov 2020 14:47:52 +0200 [thread overview]
Message-ID: <83zh33neyv.fsf@gnu.org> (raw)
In-Reply-To: <m2o8jj57po.fsf@gmail.com> (message from Helmut Eller on Fri, 27 Nov 2020 13:01:55 +0100)
> From: Helmut Eller <eller.helmut@gmail.com>
> Date: Fri, 27 Nov 2020 13:01:55 +0100
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> > Emacs 28 will have a make_unibyte_string function. Before that, you
> > have to resort to calling the unibyte-string function directly.
>
> But that's only for passing bytes from C to Lisp. What about the other
> direction?
Why do you need that? The concept of unibyte vs multibyte strings
exists only in Lisp; in C you just have a sequence of 'char' bytes,
and the way you interpret it depends on your C code.
If you have some specific use case where this looks like a necessity,
can you describe that use case?
next prev parent reply other threads:[~2020-11-27 12:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 10:43 Some dynamic module questions Helmut Eller
2020-11-27 11:50 ` Philipp Stephani
2020-11-27 12:01 ` Helmut Eller
2020-11-27 12:17 ` Zhu Zihao
2020-11-27 12:25 ` Helmut Eller
2020-11-27 12:47 ` Eli Zaretskii [this message]
2020-11-27 12:59 ` Helmut Eller
2020-11-27 13:29 ` Eli Zaretskii
2020-11-27 13:32 ` Eli Zaretskii
2020-11-27 13:54 ` Vasilij Schneidermann
2020-11-27 15:09 ` Eli Zaretskii
2020-11-27 15:21 ` Vasilij Schneidermann
2020-11-27 15:26 ` Eli Zaretskii
2020-12-02 11:43 ` Philipp Stephani
2020-12-03 5:30 ` Richard Stallman
2020-12-03 8:08 ` Lars Ingebrigtsen
2020-12-03 8:42 ` Helmut Eller
2020-12-03 11:49 ` Philipp Stephani
2020-12-03 15:13 ` Stefan Monnier
2020-12-06 17:04 ` Philipp Stephani
2020-11-27 14:06 ` Stefan Monnier
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=83zh33neyv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@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).