mq_timedsend & mq_timedreceive

[Jonathan Larmour]

Dmitriy Korovkin wrote:
> Nick, Jonathan
> Does it mean I may do them?!  
> Yesturday I found that I'd be glad to have sem_timedwait and 
> pthread_mutextimedlock. I don't see a problem with implementing it but 
> standards... Huh, actually asking around brought me that QNX guys included 
> this into their manual pages and LynxOS guys seems to do this too. Why we 
> shouldn't do this? At least, some things that are almost reqired by that 
> ^&*@^$&*@ ISaGRAF PRO target.

Feel free. It's not a priority for us though so the ball is in your court 
if you want it.

But do take care with your treatment of error conditions, for example I 
had to add something to take care of invalid timeval nanosecond values 
causing an EINVAL error. You should refer closely to the standard for 
this. See <http://www.opengroup.org/onlinepubs/007904975/mindex.html>

Jifl
-- 
eCosCentric       http://www.eCosCentric.com/       <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine