From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philipp Stephani
On Tue, Dec 19, 2017 at 2:29 AM, Philipp Stephani <p.stephani2@gmail.com= a>> wrote:
>
>
> Eli Zaretskii <el= iz@gnu.org> schrieb am Mo., 18. Dez. 2017 um 21:19 Uhr:
>>
>> >=C2=A0 >=C2=A0 >=C2=A0 > +The keyword argument OBJECT= -TYPE specifies which Lisp type is
>> > used to
>> >=C2=A0 >=C2=A0 >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^
>> >=C2=A0 >=C2=A0 >=C2=A0 Shouldn't that be `:object-ty= pe' (including quotes)?
>> >=C2=A0 >=C2=A0 >
>> >=C2=A0 >=C2=A0 > Depending on whether we can use &ke= y in a docstring in core. If
>> > so, then this one is correct, see
>> >=C2=A0 e.g.
>> >=C2=A0 >=C2=A0 the
>> >=C2=A0 >=C2=A0 > docstring of should-error.
>> >=C2=A0 >
>> >=C2=A0 >=C2=A0 IMO, the doc string of should-error is no le= ss confusing than this
>> >=C2=A0 >=C2=A0 one, because it expects something like "= ;:type 'foo".
>> >=C2=A0 >
>> >=C2=A0 > Arguably yes. Though that has been the convention = for cl-lib
>> > functions for a while.
>> >
>> >=C2=A0 cl-lib enjoyed being in the shadows for too long.=C2=A0= I don't think we
>> >=C2=A0 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?