On Fri, 1 Nov 2019, Ondřej Surý wrote:
> Hi Julia,
>
> thanks for the quick response.
>
> > On 1 Nov 2019, at 14:09, Julia Lawall wrote:
> >
> > This is not possible. ... describes control-flow paths. Nothing happens
> > after a return. Your attempt above would match functions where all
> >
Hi Julia,
thanks for the quick response.
> On 1 Nov 2019, at 14:09, Julia Lawall wrote:
>
> This is not possible. ... describes control-flow paths. Nothing happens
> after a return. Your attempt above would match functions where all
> control-flow paths end with return (ISC_R_SUCCESS);,
On Fri, 1 Nov 2019, Ondřej Surý wrote:
> Hi,
>
> we changed our allocator (wrapper) function to assert() instead of returning
> ISC_R_MEMORY.
>
> As you can imagine there’s a lot of checks down the road that needs to be
> cleaned up,
> so I am looking for a way to detect function that only
Hi,
we changed our allocator (wrapper) function to assert() instead of returning
ISC_R_MEMORY.
As you can imagine there’s a lot of checks down the road that needs to be
cleaned up,
so I am looking for a way to detect function that only does:
isc_result_t
foo(…) {
…
return (ISC_R_SUCCESS);
}