| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Joe Nelson <joe(at)begriffs(dot)com> |
| Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Chapman Flack <chap(at)anastigmatix(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: Make use of C99 designated initialisers for nulls/values arrays |
| Date: | 2019-10-21 18:13:19 |
| Message-ID: | 20191021181319.GW6962@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greetings,
* Joe Nelson (joe(at)begriffs(dot)com) wrote:
> > Is it possible to define the macro to be {} where supported and {0}
> > where needed? Something like:
>
> If it's being put behind a macro then *stylistically* it shouldn't
> matter whether {} or {0} is chosen, right? In which case {0} would
> be a better choice because it's supported everywhere.
The problem with {0} in the first place is that it doesn't actually work
in all cases... Simple cases, yes, but not more complex ones. It's
unfortunate that there isn't a general solution here that works across
platforms (even if it involved macros..), but that seems to be the case.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Atkins | 2019-10-21 18:20:26 | Re: jsonb_set() strictness considered harmful to data |
| Previous Message | Joe Nelson | 2019-10-21 18:03:07 | Re: Proposal: Make use of C99 designated initialisers for nulls/values arrays |