From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: String encoding in json.c
Date: Wed, 27 Dec 2017 18:08:47 +0200 [thread overview]
Message-ID: <83r2rggnlc.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkRAPfumUxmKDCKp_jQPHfJE-C=Ps=1oo9km1TgJDjv1ag@mail.gmail.com> (message from Philipp Stephani on Tue, 26 Dec 2017 21:42:54 +0000)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Tue, 26 Dec 2017 21:42:54 +0000
> Cc: emacs-devel@gnu.org
>
> And the fact that the internal representation is documented doesn't
> mean we can draw the conclusions like that.
>
> Why? Clearly we can make use of documented information?
Because we are not Microsoft: we do document some internal details
when we think this will help Lisp programmers and people who work on
the core. We even have a chapter named "Internals" in the manual, and
that definitely doesn't mean those descriptions are a contract that
cannot be changed at will.
IOW, the ELisp manual is no more "official" and "reliable" than
comments in the code.
> For starters, the
> documentation doesn't tell all the story: the 2-byte representation of
> raw bytes is not described there.
>
> What's the 2-byte representation?
See CHAR_BYTE8_HEAD_P and its users.
(I didn't respond to your other points because I don't see this
discussion going anywhere where I could be of use.)
next prev parent reply other threads:[~2017-12-27 16:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 14:26 String encoding in json.c Philipp Stephani
2017-12-23 14:43 ` Eli Zaretskii
2017-12-23 15:31 ` Philipp Stephani
2017-12-23 15:53 ` Eli Zaretskii
2017-12-23 17:27 ` Philipp Stephani
2017-12-23 18:18 ` Eli Zaretskii
2017-12-26 21:42 ` Philipp Stephani
2017-12-27 16:08 ` Eli Zaretskii [this message]
2017-12-24 20:48 ` Dmitry Gutov
2017-12-25 16:21 ` Eli Zaretskii
2017-12-25 20:51 ` Dmitry Gutov
2017-12-26 4:35 ` Eli Zaretskii
2017-12-26 21:50 ` Philipp Stephani
2017-12-27 2:00 ` Dmitry Gutov
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=83r2rggnlc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@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).