Gilles Chanteperdrix wrote: > The problem is that we would have to store this additional > information in the pthread_attr_t structure. And in order to allow > users to include and use the Xenomai API and the native pthread API > at the same time, Xenomai use the same definition for all the > pthread_* types as the native pthread API, and we do not know if the > native API has room for an additional string.
Which are the space constraints here ? Do we have a fixed amount of bytes that maybe inside the pthread_t structure ? Is there a compatibility issue to older Xenomai versions ? I find the function pthread_attr_set_name_np() more natural than the other function, because normally one decides upon the name of a thread at startup time, not afterwards. Having both options should be enough for everybody, and is somehow consistent with the VxWorks API that you support as well. Best regards, Daniel Schnell. _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
