Date: Tue, 14 Apr 2026 10:00:42 -0700
On Tuesday, 14 April 2026 06:31:22 Pacific Daylight Time Zhao YunShan via Std-
Proposals wrote:
> First, replacing function symbol at link time is a proven approach; g++
> --wrap has been doing this for years. Promoting this compiler flag feature
> to a native language feature would enhance code readability and make it
> effortless for developers to apply. Why not do it?
Why does it have to be a *Standard* feature? I'm not doubting the usefulness,
I'm just asking whether it needs to be in the Standard.
See also Sebastian's reply, showing there are different interception techniques
for different conditions, none of which the Standard is aware of. There's no
way to have a *single* native language feature that will work for all of those
conditions. So is it worth standardising one way of interception that doesn't
always work?
Proposals wrote:
> First, replacing function symbol at link time is a proven approach; g++
> --wrap has been doing this for years. Promoting this compiler flag feature
> to a native language feature would enhance code readability and make it
> effortless for developers to apply. Why not do it?
Why does it have to be a *Standard* feature? I'm not doubting the usefulness,
I'm just asking whether it needs to be in the Standard.
See also Sebastian's reply, showing there are different interception techniques
for different conditions, none of which the Standard is aware of. There's no
way to have a *single* native language feature that will work for all of those
conditions. So is it worth standardising one way of interception that doesn't
always work?
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Data Center - Platform & Sys. Eng.
Received on 2026-04-14 17:00:45
