[pfx-dev] Re: [PATCH] Fix missing #include statements

2025-06-12 Thread Wietse Venema via Postfix-devel
Richard Hansen via Postfix-devel: > >> The patch is adopted. > > > > And reverted, because every Postfix .h file is included > > after the .c file has already included . > > The story behind this patch: I am working on another feature that I want > to propose to you and the rest of the community

[pfx-dev] Re: pipemap lookup implementation question

2025-06-12 Thread Wietse Venema via Postfix-devel
Richard Hansen via Postfix-devel: > Hi all, > > I'm trying to understand the implementation of the pipemap: lookup > function dict_pipe_lookup() [1]. Currently it copies the input query > and pipeline stage outputs to a scratch buffer, and passes the buffer as > the query for the next stage (o

[pfx-dev] Re: [PATCH] unionmap: Also insert a comma for leading empty results

2025-06-12 Thread Wietse Venema via Postfix-devel
Wietse Venema via Postfix-devel: > Richard Hansen via Postfix-devel: > > On 2025-06-11 22:26:43-04:00, Wietse Venema via Postfix-devel wrote: > > > An empty lookup result is generally not allowed in Postfix. It's > > > enforced in maps_find(), instead of in each indiividual dict_xxx.c > > > impleme

[pfx-dev] Re: [PATCH] unionmap: Also insert a comma for leading empty results

2025-06-12 Thread Wietse Venema via Postfix-devel
Richard Hansen via Postfix-devel: > On 2025-06-11 22:26:43-04:00, Wietse Venema via Postfix-devel wrote: > > An empty lookup result is generally not allowed in Postfix. It's > > enforced in maps_find(), instead of in each indiividual dict_xxx.c > > implementation. > > Gotcha. I think it would be