From: storm@cua.dk (Kim F. Storm)
Cc: Richard Stallman <rms@gnu.org>, emacs-devel@gnu.org
Subject: Re: struct.el -- a package to encode/decode binary data
Date: 21 Mar 2002 14:31:56 +0100 [thread overview]
Message-ID: <5xbsdigi7n.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <Pine.SUN.3.91.1020321131138.8844C-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On Thu, 21 Mar 2002, Richard Stallman wrote:
>
> > Is there some specific reason not to use unibyte strings here?
>
> They are simply not needed here (AFAICS).
On the surface, it looks "obvious" to use unibyte strings for
data which is known to be - and processed as - byte-oriented
data.
But I guess you are right that it isn't strictly necessary even for
byte-oriented data, so I will avoid the final conversion to unibyte --
if unibyte-ness is really needed, the caller can do the conversion.
I've now changed the struct.el code to operate on a vector instead of
a string, so in my case it really doesn't matter anymore.
> IMO, unibyte strings
> should not be used unless absolutely necessary, ideally never.
Am I right in assuming that aref, aset, and substring are potentially
much slower on a multibyte string than on a unibyte string? Probably
not noticeable if you just look at a single char from a string, but
what if you loop over a string (forwards or backwards)?
I can see there is some caching in string_char_to_byte for multiple
accesses to the same string, but it breaks as soon as you operate on more
than one string e.g. in a loop.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-21 13:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SUN.3.91.1020319133840.17982G-100000@is>
2002-03-19 14:34 ` struct.el -- a package to encode/decode binary data Kim F. Storm
2002-03-19 21:27 ` Thien-Thi Nguyen
2002-03-21 9:04 ` Richard Stallman
2002-03-21 11:15 ` Eli Zaretskii
2002-03-21 13:31 ` Kim F. Storm [this message]
2002-03-21 14:56 ` Eli Zaretskii
2002-03-21 15:36 ` Kim F. Storm
2002-03-21 16:58 ` Stefan Monnier
2002-03-21 19:45 ` Eli Zaretskii
2002-03-22 1:05 ` Stefan Monnier
2002-03-22 11:04 ` Eli Zaretskii
2002-03-22 0:37 ` Miles Bader
2002-03-23 2:35 ` Richard Stallman
2002-03-21 16:53 ` Stefan Monnier
2002-03-23 2:36 ` Richard Stallman
2002-03-22 1:30 Kenichi Handa
-- strict thread matches above, loose matches on Subject: below --
2002-03-22 1:25 Kenichi Handa
2002-03-22 1:27 ` Stefan Monnier
2002-03-18 23:12 Kim F. Storm
2002-03-19 0:25 ` Miles Bader
2002-03-19 7:02 ` Eli Zaretskii
2002-03-19 12:34 ` Stefan Monnier
2002-03-19 14:38 ` Eli Zaretskii
2002-03-19 14:33 ` Luke Gorrie
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=5xbsdigi7n.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@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).