diff options
author | Andrew Clayton <a.clayton@nginx.com> | 2024-04-17 15:50:40 +0100 |
---|---|---|
committer | Andrew Clayton <a.clayton@nginx.com> | 2024-04-25 15:15:19 +0100 |
commit | 31cec908cd9d431eb8632b53b9bbd96caac56bfd (patch) | |
tree | 1fe4d6f1d5040fb14a0c11a9d0ca8f4e30260c6b /test/test_php_isolation.py | |
parent | 33c978cc24de3110b763354d97a907982f664b23 (diff) | |
download | unit-31cec908cd9d431eb8632b53b9bbd96caac56bfd.tar.gz unit-31cec908cd9d431eb8632b53b9bbd96caac56bfd.tar.bz2 |
configuration: Constify more pointers
This continues the patch series constifying various pointers in the
configuration sub-system.
This is done as a separate commit as it involved a _slightly_ more
invasive change in nxt_conf_get_string().
While it takes a value parameter that is never modified, simply making
it const results in
CC build/src/nxt_conf.o
src/nxt_conf.c: In function ‘nxt_conf_get_string’:
src/nxt_conf.c:170:20: error: assignment discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers]
170 | str->start = value->u.str.start;
| ^
due to the assignment operator. Making value const will allow for
numerous other constification and seeing as we are not modifying it,
seems worthwhile.
We can get around the warning by casting ->u.{str,string}.start
Reviewed-by: Zhidao HONG <z.hong@f5.com>
Signed-off-by: Andrew Clayton <a.clayton@nginx.com>
Diffstat (limited to 'test/test_php_isolation.py')
0 files changed, 0 insertions, 0 deletions