On Fri, Aug 17, 2018 at 03:26:23PM +0200, Kamil Rytarowski wrote:
> On 17.08.2018 15:16, Thomas Klausner wrote:
> > Hi!
> >
> > Does anyone know why NetBSD has udata defined as intptr_t in kqueue(3)?
> >
> > I.e.:
> >
> > EV_SET(&kev, ident, filter, flags, fflags, data, udata);
> >
> > whe
On Fri, Aug 17, 2018 at 03:16:20PM +0200, Thomas Klausner wrote:
> Does anyone know why NetBSD has udata defined as intptr_t in kqueue(3)?
It's been discussed over the years. It is supposed to be opaque and
pointers don't really qualify for that. I.e. in theory, there are
integers that are not val
Hi!
Does anyone know why NetBSD has udata defined as intptr_t in kqueue(3)?
I.e.:
EV_SET(&kev, ident, filter, flags, fflags, data, udata);
where the values are defined as:
struct kevent {
uintptr_t ident;/* identifier for this event */
uint32_t filt
