This is the mail archive of the ecos-patches@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: mq_timedsend & mq_timedreceive


OK, I'll try to add the required stuff on the nearest weekend.
Regards,
-- 
Dmitriy

On Tue, 14 Jan 2003, Jonathan Larmour wrote:

> Date: Tue, 14 Jan 2003 07:10:12 +0000
> From: Jonathan Larmour <jifl@ecoscentric.com>
> To: Dmitriy Korovkin <dkorovkin@rambler.ru>
> Cc: Nick Garnett <nickg@ecoscentric.com>, ecos-patches@sources.redhat.com
> Subject: Re: mq_timedsend & mq_timedreceive
> 
> 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
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]