Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compilation Warning([ezxml.c.]/ [line 364]): operation on 's' may be undefined [-Wsequence-point] #6

Open
rexlim820220 opened this issue Apr 28, 2023 · 0 comments · May be fixed by #7

Comments

@rexlim820220
Copy link

Summary

Compilation warning arise in ezxml.c for gcc compiler to parse an inline expression of condition which breaks a while loop.

The code snippet triggering the warning took place in line 364, inside function ezxml_internal_dtd(), which aims to parse default attributes such as .

Steps to reproduce

The environment is under CentOS Linux release 7.9.2009 (Core), with gcc (GCC) 7.3.0.

Compilation rules were defined ias below, with ezxml.h located in ${PROJECT_BINARY_DIR} and ezxml.c in the same directory with CMakeList.txt.

project(APP C)
include_directories(${PROJECT_BINARY_DIR})

# source files
set(CLI_SRC ezxml.c)

add_executable(APP ${CLI_SRC})
...

What is the current bug(warning) behavior?

gcc shows warning as below:

[ 85%] Building C object cli/CMakeFiles/ezxml.c.o
/home/cli/ezxml.c: In function 'ezxml_internal_dtd':
/home/cli/ezxml.c:364:26: warning: operation on 's' may be undefined [-Wsequence-point]
             while (*(n = ++s + strspn(s, EZXML_WS)) && *n != '>') {
                          ^

Possible fixes

My suggestion would be removing the inline condition expression, and adopting an multi-line expression instead.

Such as

while (*n != '>') {
                ++s;
                if (*(n = s + strspn(s, EZXML_WS)) == 0) { break; }
                ...

Labels

/label ~bug ~reproduced ~needs-investigation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant