Either I''ve been up too late, or the timeout value passed to Ipc.new isn''t actually saved anywhere. Am I wrong? Anyway, I''ve added docs and a test suite for win32-ipc. Feel free to take a look and make sure there aren''t any glaring errors. Thanks. Dan PS - I''m hoping to release win32-event 0.2.0 and win32-ipc 0.1.0 this weekend unless there are any objections. _________________________________________________________________ Lose those love handles! MSN Fitness shows you two moves to slim your waist. http://fitness.msn.com/articles/feeds/article.aspx?dept=exercise&article=et_pv_030104_lovehandles
Hi,> > Either I''ve been up too late, or the timeout value passed to Ipc.new isn''t > actually saved anywhere. Am I wrong? >The Ipc.new is almost nothing for itself. I recommend you should not call Ipc.new directly. Normally, it is called by other classes like changenotify, mutex, semaphore etc. Regards, Park Heesob --MIME Multi-part separator--
> -----Original Message----- > From: win32utils-devel-bounces@rubyforge.org > [mailto:win32utils-devel-bounces@rubyforge.org] On Behalf Of > win32utils-devel@rubyforge.org > Sent: Wednesday, April 28, 2004 10:43 PM > To: win32utils-devel@rubyforge.org > Subject: Re:[Win32utils-devel] win32-ipc bug? > > > Hi, > > > > Either I''ve been up too late, or the timeout value passed > to Ipc.new > > isn''t > > actually saved anywhere. Am I wrong? > > > The Ipc.new is almost nothing for itself. > I recommend you should not call Ipc.new directly. > Normally, it is called by other classes like changenotify, > mutex, semaphore etc.Right, I just mean that Ipc.new requires a mandatory argument that doesn''t appear to be used. rb_define_singleton_method(cIpc,"new",ipc_new,1); Should I change it from 1 to 0? I will unless you tell me otherwise. Dan
> > Right, I just mean that Ipc.new requires a mandatory argument that > doesn''t appear to be used. > > rb_define_singleton_method(cIpc,"new",ipc_new,1); > > Should I change it from 1 to 0? I will unless you tell me otherwise. > > Dan >The required argument is an object handle for ipc objects like event, semaphore, mutex etc. It is used for waiting of that object. It is called by other ipc modules For example, you can see in event.c of win32-event args[0] = UINT2NUM((DWORD)ptr->hEvent); rb_call_super(1,args); Park Heesob --MIME Multi-part separator--