https://bugs.exim.org/show_bug.cgi?id=3024
--- Comment #4 from Andreas Metzler <eximus...@bebt.de> --- (In reply to Jeremy Harris from comment #3) > The option on the condition turns out to be not too invasive to code, > assuming it's done as a comma-sep option after the condition name. [...] > How do people feel? Is it worth adding this syntax? There are no other > options on expansion-conditions at this time. It seems to be a little bit adhoc to add options to /some/ operators to not touch $value since reduce also touches $value. I think reduce's $value should somehow "trump" whatever the inner expansions do. However then a further question pops up: "At the end of a reduce expansion, the values of $item and $value are restored to what they were before." What is "before" in that context? $value as set by the inner expansion? How about instead changing reduce to use a different temporary variable instead of $value? cu Andreas -- You are receiving this mail because: You are on the CC list for the bug. -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-dev-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
