RTEMS | Draft: cpukit/posix/aio*: Create notification at request completion (!118)

[Alessandro Nardin (@AlessandroNardin)]

Alessandro Nardin commented on a discussion on cpukit/posix/src/aio_misc.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/118#note_109432

 > +        if ( result != 0 ){
 > +        //handle error
 > +        }
 > +        result = pthread_attr_setdetachstate(
 > +          attr, 
 > +          PTHREAD_CREATE_DETACHED
 > +          );
 > +        if ( result != 0){
 > +        //handle error
 > +        }
 > +      }
 > +
 > +      result = pthread_create( 
 > +        &thread,
 > +        attr,
 > +        (void * (*)(void *)) sig->sigev_notify_function,

Now it should be right if I understood correctly what you meant. I passed the sigevent structure as a parameter to the wrapper function since it contains the pointer to the function and its parameters.

I was curious to understand why this is necessary. Is it to improve code readability, or are there other reasons?

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/118#note_109432
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20240717/72283196/attachment-0001.htm>