From: Vibhav Pant <vibhavp@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, TV Raman <raman@google.com>,
emacs-devel@gnu.org
Subject: Re: JSON->lisp Mapping: Hash vs AList
Date: Tue, 19 Dec 2017 09:20:54 +0530 [thread overview]
Message-ID: <CA+T2Sh009gbG6zOXaB+_WS7t0M5+ktp-RKaUekxAWY0=VXLzJA@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkTpZ_KD1PfiV0pVYpKBOuuDXSHkzdZCxLVrLxx+ZdLOZg@mail.gmail.com>
On Tue, Dec 19, 2017 at 2:29 AM, Philipp Stephani <p.stephani2@gmail.com> wrote:
>
>
> Eli Zaretskii <eliz@gnu.org> schrieb am Mo., 18. Dez. 2017 um 21:19 Uhr:
>>
>> > > > > +The keyword argument OBJECT-TYPE specifies which Lisp type is
>> > used to
>> > > > ^^^^^^^^^^^
>> > > > Shouldn't that be `:object-type' (including quotes)?
>> > > >
>> > > > Depending on whether we can use &key in a docstring in core. If
>> > so, then this one is correct, see
>> > e.g.
>> > > the
>> > > > docstring of should-error.
>> > >
>> > > IMO, the doc string of should-error is no less confusing than this
>> > > one, because it expects something like ":type 'foo".
>> > >
>> > > Arguably yes. Though that has been the convention for cl-lib
>> > functions for a while.
>> >
>> > cl-lib enjoyed being in the shadows for too long. I don't think we
>> > should let that continue any longer, we should fix that.
>> >
>> > OK, what's your suggestion?
>>
>> I thought I wrote that above.
>
>
> I've attached a new version of the patch.
fns.c has `get_key_arg', which accomplishes what json_parse_object_type is doing
here, and allows the list of keyword arguments to be extended (like in
`make-hash-table`). Do you think that could be used here instead?
Thanks,
Vibhav
--
Vibhav Pant
vibhavp@gmail.com
next prev parent reply other threads:[~2017-12-19 3:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 1:39 JSON->lisp Mapping: Hash vs AList raman
2017-12-12 13:08 ` Nicolas Petton
2017-12-12 15:52 ` raman
2017-12-13 22:37 ` Philipp Stephani
2017-12-14 0:00 ` T.V Raman
2017-12-14 16:27 ` Eli Zaretskii
2017-12-16 22:24 ` Philipp Stephani
2017-12-17 15:53 ` Eli Zaretskii
2017-12-17 17:44 ` Philipp Stephani
2017-12-17 20:07 ` Eli Zaretskii
2017-12-18 19:55 ` Philipp Stephani
2017-12-18 20:19 ` Eli Zaretskii
2017-12-18 20:59 ` Philipp Stephani
2017-12-19 3:50 ` Vibhav Pant [this message]
2017-12-19 17:49 ` Philipp Stephani
2017-12-19 17:08 ` Eli Zaretskii
2017-12-19 17:22 ` Philipp Stephani
2017-12-18 16:15 ` Clément Pit-Claudel
2017-12-19 17:50 ` Philipp Stephani
2017-12-15 4:13 ` Vibhav Pant
2017-12-16 22:25 ` Philipp Stephani
2017-12-18 20:26 ` [PATCH] Accept alists when serializing JSON Philipp Stephani
2017-12-20 5:58 ` Vibhav Pant
2017-12-22 13:55 ` Philipp Stephani
2017-12-24 17:16 ` Vibhav Pant
2017-12-26 20:46 ` Philipp Stephani
2017-12-24 13:00 ` Philipp Stephani
2017-12-16 22:34 ` JSON->lisp Mapping: Hash vs AList Stefan Monnier
2017-12-16 22:38 ` Philipp Stephani
2017-12-17 0:54 ` Paul Eggert
2017-12-17 2:41 ` Stefan Monnier
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='CA+T2Sh009gbG6zOXaB+_WS7t0M5+ktp-RKaUekxAWY0=VXLzJA@mail.gmail.com' \
--to=vibhavp@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=raman@google.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).