Hello, thank you for your reply.
2014-06-12 23:05 GMT+09:00 Florian Westphal <fw@xxxxxxxxx>:
> Ken-ichirou MATSUZAWA <chamaken@xxxxxxxxx> wrote:
>> Should we clear errno in that cmp_zone() before return?
>
> I *think* the best approach would be to not clear it
> at this time.
>
> would solve. I don't think callers/users should rely on errno
> having any particular value after nfct_cmp() returns, regardless
> of the return value.
I'd read same thing in err30-c and I'll follow your best thought.
Sorry for offtopic:
I think go lang people made an unlikable decision. Its function
can return multiple value, and its c wrapper suite (cgo) normally
returns result and errno as error. They have an ideom like
if retval, err := function(); err != nil {
error_processing()
}
Things you told me is very helpful for wrapping by golang, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
