Re: jsonapi type fixups - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: jsonapi type fixups
Date
Msg-id 0a440c8c-6419-4c27-aac1-c64efb580cc9@dunslane.net
Whole thread Raw
In response to jsonapi type fixups  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: jsonapi type fixups
Re: jsonapi type fixups
List pgsql-hackers
On 2024-06-18 Tu 7:48 AM, Peter Eisentraut wrote:
> I have this patch series that fixes up the types of the new 
> incremental JSON API a bit.  Specifically, it uses "const" throughout 
> so that the top-level entry points such as pg_parse_json_incremental() 
> can declare their arguments as const char * instead of just char *.  
> This just works, it doesn't require any new casting tricks.  In fact, 
> it removes a few unconstify() calls.
>
> Also, a few arguments and variables that relate to object sizes should 
> be size_t rather than int.  At this point, this mainly makes the API 
> better self-documenting.  I don't think it actually works to parse 
> larger than 2 GB chunks (not tested).



I think this is mostly OK.

The change at line 1857 of jsonapi.c looks dubious, though. The pointer 
variable p looks anything but constant. Perhaps I'm misunderstanding.

It would also be nice to reword the comment at line 3142 of jsonfuncs.c, 
so it can still fit on one line.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm
Next
From: Ranier Vilela
Date:
Subject: Re: confusing valgrind report about tuplestore+wrapper_handler (?) on 32-bit arm