After a period of trial and error, I found that the vxWorks compiler is very sensitive to the definition of local variables, which must be defined at the beginning of the function, or compile error: parse Error near int, etc.
As shown in the figure:
As shown in the figure:
Putting the iRet definition at the beginning solves this problem, as shown in the figure below:
Read More:
- make Error: error: cast from ‘int32_t*’ {aka ‘int*’} to ‘int’ loses precision [-fpermissive]
- Debug | AttributeError: ‘numpy.int64‘ object has no attribute ‘to_pydatetime‘
- go :Multiple-value strconv.Atoi() (int, error) in single-value context
- ERROR：expected initializer before “int”
- TypeError: int() can’t convert non-string with explicit base
- Can’t multiply sequence by non int of type ‘float’
- Arithmetic overflow error converting identity to data type int
- Keil ：error: identifier “int8_ T “is undefined
- Keil : error: identifier “int8_ T “is undefined
- Type error: sequence item 0: expected STR instance, int found
- TypeError: unsupported operand type(s) for *: ‘range‘ and ‘int‘
- How to Solve Int Data overflow error
- The Vue elementui switch button uses an int type value
- The reason and solution of the error of join function: sequence item 0: expected STR instance, int found
- Error response from daemon: failed to parse mydockerfile-centos: ENV must have two arguments
- node url.parse()
- Undefined reference to ‘CV:: imread (CV:: String const & int)’
- JSON parse error: invalid UTF-8 solution series
- Python: How to Fix “Ord() expected string of length 1, but int found”
- When websocket transmits JSON text, the parse method reports an error