Re: ./configure --enable-check-lisp-object-type

[Stefan Monnier <monnier@iro.umontreal.ca>]

> For the first time in a while I enabled the Lisp object type, and I was
> given a wall of

I've been using it for many many years.

> dispnew.c:6593:1: note: in expansion of macro ‘DEFUN’
>  6593 | DEFUN ("internal-show-cursor-p", Finternal_show_cursor_p,
>       | ^~~~~
> lisp.h:3179:5: warning: missing braces around initializer [-Wmissing-braces]
>  3179 |     {{{{ PVEC_SUBR << PSEUDOVECTOR_AREA_BITS },                         \
>       |     ^
>
> for every DEFUN.  That's new, isn't it?  (This is on Debian/bookworm.)

Yes, it's new enough that I haven't reported it yet.

> This is from this:
>
> #define DEFUN(lname, fnname, sname, minargs, maxargs, intspec, doc)	\
>   SUBR_SECTION_ATTRIBUTE                                                \
>   static union Aligned_Lisp_Subr sname =                                \
>      {{{ PVEC_SUBR << PSEUDOVECTOR_AREA_BITS },				\
>        { .a ## maxargs = fnname },					\
>        minargs, maxargs, lname, {intspec}, 0}};				\
>    Lisp_Object fnname
>
> That seems like beaucoup de braces, so is that a gcc bug or something?
> (Adding more braces makes compilation fail.)

I don't know the syntax of C initializers well enough to judge, but
I wasn't able to silence the warning by tweaking the code, so far.


        Stefan