Re: [Opencxx-users] Checking of return codes

[Stefan S. <se...@sy...>]

SF Markus Elfring wrote:
>>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?

I don't understand what you are asking. Function declarations / definitions can of course be
checked for return types. Overload resolution comes into play when you find a
function call expression and you want to find out what the thing is that is being
called. A function ? A call operator ? Which version, dependent on the type the
argument evaluates to ?

> Is a usage scanner for return values available already?

What are you referring to ? Function declarations or function call expressions ?

> Can an algorithm be reused to manage and iterate over the references?

What do you mean by reuse ?

Regards,
		Stefan