From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, dancol@dancol.org
Cc: 23487@debbugs.gnu.org
Subject: bug#23487: 25.0.93; Modules: add functionality to create and copy unibyte strings
Date: Mon, 09 May 2016 18:06:41 +0000 [thread overview]
Message-ID: <CAArVCkTkrXR3_6oOcuhgZ13Wg03OTDV74seFNCOsCjiUQBjp+w@mail.gmail.com> (raw)
In-Reply-To: <83r3dbcfju.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Mo., 9. Mai 2016 um 19:22 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Mon, 09 May 2016 18:45:19 +0200
> >
> > Currently creating unibyte strings with the C module API is rather
> > convoluted: one has to create a list with the individual bytes and then
> > call `unibyte-string', requiring lots of memory allocations. Given that
> > creating a unibyte string is more fundamental than creating a multibyte
> > string, I propose adding functions to create and extract unibyte strings
> > that exactly mirror the existing support for multibyte strings.
>
> Can you explain why you need to create unibyte strings, or describe a
> use case where this would be required?
>
I don't have a concrete use case per se, but the API feels incomplete
without this functionality, especially given that creation of multibyte
strings is supported and uses unibyte strings under the hood.
I'll let +Daniel Colascione <dancol@dancol.org> chime in for his opinion.
[-- Attachment #2: Type: text/html, Size: 1506 bytes --]
next prev parent reply other threads:[~2016-05-09 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:45 bug#23487: 25.0.93; Modules: add functionality to create and copy unibyte strings Philipp Stephani
2016-05-09 17:22 ` Eli Zaretskii
2016-05-09 18:06 ` Philipp Stephani [this message]
2016-05-09 18:49 ` Eli Zaretskii
2020-08-12 2:31 ` Stefan Kangas
2020-10-01 12:12 ` Stefan Kangas
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=CAArVCkTkrXR3_6oOcuhgZ13Wg03OTDV74seFNCOsCjiUQBjp+w@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=23487@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
/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).