Tejun Heo wrote:
quoted text > * Passing NULL as data to callback which takes non-void pointer
> triggers warning. I think this should be allowed. Something like
> the following?
Please ignore the last sentence.
quoted text > * Allowing non-pointer integral types which fit into pointer would be
> nice. It's often convenient to pass integers to simple callbacks.
>
> The following macro kinda-sorta achieves the above two but it doesn't
> consider promotion of integer types and thus is too strict. There
> gotta be some way.
What should be do are
* Check that the threadfn's argument fits into void *.
* Trigger overflow in implicit constant conversion warning if the
specified data is too large for the argument type.
Tricky...
--
tejun
--
unsubscribe notice To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Messages in current thread:
Re: [PATCH 0/6] RFC: Typesafe callbacks , Tejun Heo , (Sun Jan 20, 9:00 am)