Re: [exim/exim] Spec, examples of different lookup syntax: if it shouldn't have read as suggested, it should explain why not (Issue #3216)
Jeremy Harris via Exim-dev <[email protected]> Wed, 15 Apr 2026 09:37:17 +0100
| Newsgroups | gmane.mail.exim.devel |
|---|---|
| Message-ID | <[email protected]> |
On 2026/04/15 12:51 AM, maeqs5a via Exim-dev wrote: > doesn't the paragraph that was patched above is reiterated at a concrete example for the possible confusion (https://code.exim.org/exim/exim/src/commit/e8a71fcd7027ff383b06bfe715836c32b18eaea2/doc/doc-docbook/spec.xfpt#L6812-L6819 ) ? A) that question isn't good grammar itself, so I'm having to guess what you are asking B) no, the lines you point to are calling out a separate complexity issue > I think it confuses the 1st and 2nd kind. If it shouldn't have read as in > then I do believe it should explain why it shouldn't read like that. I see no reason why you should want to invent the change in the first place. I do feel that this could be better expressed though: "especially as the lists that may contain the second kind are always expanded before being processed as lists" change to "especially as lists (which may contain elements that are the second kind of lookup) are always expanded before being processed as lists" -- Cheers, Jeremy