From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Is CHAR_TO_BYTE considered to have no side-effects?
Date: Thu, 18 Apr 2002 12:44:56 -0600 (MDT) [thread overview]
Message-ID: <200204181844.g3IIiuO00449@aztec.santafe.edu> (raw)
In-Reply-To: <20020417162147.20D9.LEKTU@terra.es> (message from Juanma Barranquero on Wed, 17 Apr 2002 16:30:19 +0200)
So, can CHAR_TO_BYTE be considered, interface-wise, as side-effect free?
For most purposes, yes. Unless the surrounding code operates directly
on the marker data structures in a way that might be fooled by
creating new markers, it is ok.
prev parent reply other threads:[~2002-04-18 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 14:30 Is CHAR_TO_BYTE considered to have no side-effects? Juanma Barranquero
2002-04-18 18:44 ` Richard Stallman [this message]
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=200204181844.g3IIiuO00449@aztec.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@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).