From: Richard Stallman <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: decode-coding-string gone awry?
Date: Fri, 18 Feb 2005 09:12:41 -0500 [thread overview]
Message-ID: <E1D28s5-0008Sg-7S@fencepost.gnu.org> (raw)
In-Reply-To: <200502171208.VAA09592@etlken.m17n.org> (message from Kenichi Handa on Thu, 17 Feb 2005 21:08:02 +0900 (JST))
It's not a trivial work to change the current code (in
coding.c) to signal an error safely while doing a code
conversion. So, to check if decoding is valid or not, we
have to check all characters in a string in advance, which,
I think, slows down the operation considerably.
Does the speed of decoding for strings really matter?
Maybe not. We could try checking the characters in advance,
but only for strings.
We could also add an arg to decode-coding-string saying "don't check",
which people could use in cases where the speed really matters.
next prev parent reply other threads:[~2005-02-18 14:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 3:50 decode-coding-string gone awry? David Kastrup
2005-02-14 1:50 ` Kenichi Handa
2005-02-14 2:28 ` David Kastrup
2005-02-15 6:15 ` Richard Stallman
2005-02-15 9:31 ` David Kastrup
2005-02-15 16:17 ` Stefan Monnier
2005-02-17 10:35 ` Richard Stallman
2005-02-17 12:08 ` Kenichi Handa
2005-02-17 13:20 ` Stefan Monnier
2005-02-18 8:30 ` Kenichi Handa
2005-02-18 12:56 ` Stefan Monnier
2005-02-19 9:44 ` Richard Stallman
2005-02-18 14:12 ` Richard Stallman
2005-02-19 20:55 ` Richard Stallman
2005-02-21 1:19 ` Kenichi Handa
2005-02-22 8:41 ` Richard Stallman
2005-02-18 14:12 ` Richard Stallman [this message]
2005-02-14 13:37 ` Stefan Monnier
2005-02-14 13:50 ` David Kastrup
2005-02-14 16:57 ` Stefan Monnier
2005-02-14 17:24 ` David Kastrup
2005-02-14 18:12 ` Stefan Monnier
2005-02-14 18:41 ` David Kastrup
2005-02-14 19:30 ` Stefan Monnier
2005-02-14 20:09 ` David Kastrup
2005-02-14 20:56 ` Stefan Monnier
2005-02-14 21:07 ` David Kastrup
2005-02-14 21:29 ` Stefan Monnier
2005-02-14 21:57 ` David Kastrup
2005-02-14 21:26 ` David Kastrup
2005-02-15 17:28 ` Richard Stallman
2005-02-15 21:42 ` David Kastrup
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=E1D28s5-0008Sg-7S@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).