https://bugs.exim.org/show_bug.cgi?id=3024
--- Comment #6 from Andreas Metzler <eximusers@???> ---
(In reply to Jeremy Harris from comment #5)
[...]
> ${reduce...} is documented to use $value; we could only change it by
> adding optional behaviour, which also means syntax. At least until
> someone designs Exim version 5, we're stuck with it.
It is not that clear cut. - Some uses of reduce broke, because some other parts
of exim were enhanced/extended. So we already broke reduce for some users.
Still I think you right, breaking $value for all users would be worse than the
status-quo.
How about marking reduce deprecated and adding e.g. reduce2 which differs from
reduce only in using e.g. $red_value instead of $value as temporary variable?
This seems to be simpler and more robust to future changes than looking at all
expansion operators and extending all of them that change $value (either now at
some unknown point in the future) to have an option to not do this.
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-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
