From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Accept plists when serializing and parsing JSON Date: Sun, 03 Jun 2018 00:05:55 -0400 Message-ID: References: <87sh6awls5.fsf@gmail.com> <87in75bjvm.fsf@gmail.com> <87a7scu2qe.fsf@gmail.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1527998686 9744 195.159.176.226 (3 Jun 2018 04:04:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 3 Jun 2018 04:04:46 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 03 06:04:42 2018 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 1fPKG1-0002Pw-Es for ged-emacs-devel@m.gmane.org; Sun, 03 Jun 2018 06:04:41 +0200 Original-Received: from localhost ([::1]:33540 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fPKI8-0002KU-25 for ged-emacs-devel@m.gmane.org; Sun, 03 Jun 2018 00:06:52 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fPKHX-0002KL-9P for emacs-devel@gnu.org; Sun, 03 Jun 2018 00:06:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fPKHU-0003fQ-0M for emacs-devel@gnu.org; Sun, 03 Jun 2018 00:06:15 -0400 Original-Received: from [195.159.176.226] (port=59221 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fPKHT-0003fB-Oh for emacs-devel@gnu.org; Sun, 03 Jun 2018 00:06:11 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fPKFG-0001Yz-9Y for emacs-devel@gnu.org; Sun, 03 Jun 2018 06:03:54 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:9PuE6TA3FVfJUialcmXUdt1sWZA= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 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:225948 Archived-At: > wrote, it's "read-only from json.c"". You may hold another > interpretation, and that's just fine, but by "global state", in Emacs, I > understand things like buffer, point, mark, match data, etc... That is, > I mean exactly what Emacs adds to these functions' docstrings. From > help-fns.el > > (when (or (function-get function 'pure) > (function-get function 'side-effect-free)) > (insert "\nThis function does not change global state, " > "including the match data.")) > > This is what I mean by global state. Anything else is potentially > erudite bikeshedding in which I'm not particularly interested right now. Notice the use of "change" in that docstring. Looking up the value of a dynamically-scoped variable doesn't *change* global state, but it *uses* global state. But yes, this is quickly falling into "erudite bikeshedding" territory, so I'll stop before giving my opinion. Stefan