From: Philipp Stephani <p.stephani2@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>,
Helmut Eller <eller.helmut@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
Vasilij Schneidermann <mail@vasilij.de>
Subject: Re: Some dynamic module questions
Date: Sun, 6 Dec 2020 18:04:27 +0100 [thread overview]
Message-ID: <CAArVCkS_9SqHTKqy38bHXW1bD_fuz5WMhN+feFXkSMqnZRLzkw@mail.gmail.com> (raw)
In-Reply-To: <jwvh7p2kjp2.fsf-monnier+emacs@gnu.org>
Am Do., 3. Dez. 2020 um 16:13 Uhr schrieb Stefan Monnier
<monnier@iro.umontreal.ca>:
>
> > I agree that there should be a copy_unibyte_string_contents as well.
>
> An alternative would be to have a function like `copy_string_contents`
> which either returns bytes or a utf-8-encoded sequence of chars
> depending on whether the string was unibyte or not, and where it
> additionally returns an indication of which was the case.
>
Yes, that would be a viable alternative. (It would need a different
name, though, "copy_string_contents" is already taken.)
next prev parent reply other threads:[~2020-12-06 17:04 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAArVCkS_9SqHTKqy38bHXW1bD_fuz5WMhN+feFXkSMqnZRLzkw@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=mail@vasilij.de \
--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.