From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 34873@debbugs.gnu.org, lg.zevlg@gmail.com
Subject: bug#34873: 27.0.50; Creating unibyte string in emacs modules
Date: Thu, 27 Aug 2020 16:40:31 +0300 [thread overview]
Message-ID: <83sgc81a28.fsf@gnu.org> (raw)
In-Reply-To: <87y2m0w87z.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 27 Aug 2020 15:04:32 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: lg.zevlg@gmail.com, 34873@debbugs.gnu.org
> Date: Thu, 27 Aug 2020 15:04:32 +0200
>
> > In this case AFAIR the request was to use unibyte strings for binary
> > data, i.e. stuff that is not a string at all, which is one more reason
> > not to base the implementation on unibyte strings.
>
> Yes, the only real reason to use unibyte strings is for binary data, I
> thought?
No, that's not the use case for unibyte strings. We have bindat.el
for that. Unibyte strings is for handling text that was not yet
decoded into the internal representation, or which was encoded before
sending it to an external program or I/O port.
> Just like unibyte buffers are for data, not text, unibyte strings are
> for data, not text.
If that's what you really think, we disagree. About the only use case
which comes close (though not close enough) to what you describe is
when we hold compressed data in a buffer.
next prev parent reply other threads:[~2020-08-27 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 20:52 bug#34873: 27.0.50; Creating unibyte string in emacs modules Evgeny Zajcev
2019-03-16 7:30 ` Eli Zaretskii
2019-03-16 10:32 ` lg.zevlg
2019-03-16 12:20 ` Eli Zaretskii
2019-03-16 15:28 ` lg.zevlg
2019-03-16 16:17 ` Eli Zaretskii
2019-05-07 16:55 ` Basil L. Contovounesios
2019-05-07 18:33 ` Eli Zaretskii
2019-05-07 19:24 ` Basil L. Contovounesios
2019-05-07 19:48 ` Eli Zaretskii
2020-08-26 10:43 ` Lars Ingebrigtsen
2020-08-26 10:52 ` Eli Zaretskii
2020-08-27 13:04 ` Lars Ingebrigtsen
2020-08-27 13:40 ` Eli Zaretskii [this message]
2020-08-27 14:33 ` Noam Postavsky
2020-08-27 16:57 ` Eli Zaretskii
2020-08-27 17:13 ` Noam Postavsky
2020-08-27 17:18 ` Eli Zaretskii
2020-10-13 4:52 ` Lars Ingebrigtsen
2020-10-13 14:31 ` Philipp Stephani
2020-10-14 3:59 ` Lars Ingebrigtsen
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=83sgc81a28.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34873@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=lg.zevlg@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).