vasnprintf: Fix uninitialized values.

Hi Bruno, I was looking at the gzip CI to double check that FreeBSD was the known error "pipe-output", and it was. But I also noticed some warnings that occur on all systems that use Clang by default. Here is the steps that I used to reproduce on GNU/Linux: $ clang --version | sed 1q cla

stddef-h: Make 'unreachable' usable in C++ mode

Pierre Ossman reported in : In file included from /BUILD/gettext-0.25/gettext-tools/src/msgmerge.c:36, from /BUILD/gettext-0.25/gettext-tools/woe32dll/c++msgmerge.cc:1: /BUILD/gettext-0.25/gettext-tools/src/msgmerge.c: In function 'int main(

Re: making good use of LLMs

Paul Eggert wrote: > I just asked Gemini (2.5 Flash) that question ... > >volatile sig_atomic_t in_signal_handler = 0; >void my_signal_handler(int signum) { >in_signal_handler = 1; >} :-D A perfect example for junior programmers why they should keep their brain turned on when

Re: making good use of LLMs

On 5/27/25 14:17, Bruno Haible wrote: For example, a question like In C, is there a way to determine whether the currently executing thread is inside a signal handler? ... is generic enough, that the answer is likely correct. Heh, I just asked Gemini (2.5 Flash) that que

Re: making good use of LLMs

Paul Eggert wrote: > > They are also not defined on AIX 7.3 (cfarm119.cfarm.net). > > Thanks for fixing all that. I was lazily relying on Google searches and > Gemini, not the real thing. Welcome to the new technologies :) IMO there are two considerations when using a prior knowledge summarizat

Re: [PATCH 3/3] fcntl-h: document O_CLOFORK etc

Hi Bruno and Paul, Bruno Haible via Gnulib discussion list writes: >> +Although POSIX.1-2024 standardized @code{O_CLOFORK}, >> +@code{FD_CLOFORK} and @code{F_DUPFD_CLOFORK}, >> +they are not defined on most platforms: >> +glibc 2.41, musl libc, macOS 15.5, FreeBSD 14.2, NetBSD 10.1, OpenBSD 7.7,

Re: [PATCH 3/3] fcntl-h: document O_CLOFORK etc

On 2025-05-27 02:43, Bruno Haible wrote: They are also not defined on AIX 7.3 (cfarm119.cfarm.net). Thanks for fixing all that. I was lazily relying on Google searches and Gemini, not the real thing. Maybe I should note when I do that.

Re: strchrnul: Update doc

> macOS 15.4 added the strchrnul() function in libc. [1] Here's an improvement for users of the newest macOS SDK (that includes the header files of macOS 15.4) on older macOS versions (< 15.4). 2025-05-27 Bruno Haible strchrnul: Fix for users of the current macOS SDK. Reporte

Re: [PATCH 2/3] fcntl-h: support O_DIRECTORY

Paul Eggert wrote: > It is relatively easy to support O_DIRECTORY on platforms that > lack it, so let’s do that instead of having to work around bugs > like . Nice. Let me update the platforms list: - The configure test reports checking for working fcntl.h...

Re: [PATCH 3/3] fcntl-h: document O_CLOFORK etc

> +Although POSIX.1-2024 standardized @code{O_CLOFORK}, > +@code{FD_CLOFORK} and @code{F_DUPFD_CLOFORK}, > +they are not defined on most platforms: > +glibc 2.41, musl libc, macOS 15.5, FreeBSD 14.2, NetBSD 10.1, OpenBSD 7.7, > +Minix 3.3.0, AIX 7.1, Solaris 11.3, Cygwin 3.6.2, mingw, MSVC 14. The

Re: [PATCH 1/3] Document HAVE_WORKING_O_NO{ATIME,FOLLOW}

A small styling tweak: 2025-05-27 Bruno Haible doc: Style module name. * doc/posix-headers/fcntl.texi: Style module name with @code. diff --git a/doc/posix-headers/fcntl.texi b/doc/posix-headers/fcntl.texi index 8d018b9aa6..22e791b5a8 100644 --- a/doc/posix-headers/fcntl.texi