Re: [Opencxx-users] Checking of return codes

[SF M. E. <el...@us...>]

> That's what I suggested. Checking that the return value is actually used can be done at
> compile-time. That doesn't involve any code generation, though. Synopsis could just issue
> a message if it finds a function call with a non-void return value that is not used later on.

Can the function declaration or definition be checked for non-void types without overload resolution?

Is a usage scanner for return values available already?
Can an algorithm be reused to manage and iterate over the references?

I see two cases for further consideration.
1. A value is used in a condition expression as a temporary object.
2. The required value was assigned to a variable ago. But you do not know the amount of code between the interesting places in the analysed function.

Regards,
Markus