From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: String encoding in json.c Date: Wed, 27 Dec 2017 18:08:47 +0200 Message-ID: <83r2rggnlc.fsf@gnu.org> References: <83tvwhjyi5.fsf@gnu.org> <83mv29jv99.fsf@gnu.org> <83incxjojg.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1514390808 31059 195.159.176.226 (27 Dec 2017 16:06:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 27 Dec 2017 16:06:48 +0000 (UTC) Cc: emacs-devel@gnu.org To: Philipp Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 27 17:06:44 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eUEE6-0007mg-Vj for ged-emacs-devel@m.gmane.org; Wed, 27 Dec 2017 17:06:43 +0100 Original-Received: from localhost ([::1]:38069 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUEG5-0002Zx-MC for ged-emacs-devel@m.gmane.org; Wed, 27 Dec 2017 11:08:45 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUEFy-0002ZE-LC for emacs-devel@gnu.org; Wed, 27 Dec 2017 11:08:39 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eUEFv-0002Wd-CF for emacs-devel@gnu.org; Wed, 27 Dec 2017 11:08:38 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:40075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eUEFv-0002WH-3V; Wed, 27 Dec 2017 11:08:35 -0500 Original-Received: from [176.228.60.248] (port=4628 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eUEFu-00045C-Jy; Wed, 27 Dec 2017 11:08:34 -0500 In-reply-to: (message from Philipp Stephani on Tue, 26 Dec 2017 21:42:54 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:221434 Archived-At: > From: Philipp Stephani > 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.)