[Win32utils-devel] win32-ipc bug?

win32utils-devel at rubyforge.org win32utils-devel at rubyforge.org
Thu Apr 29 10:43:48 EDT 2004


> -----Original Message-----
> From: win32utils-devel-bounces at rubyforge.org 
> [mailto:win32utils-devel-bounces at rubyforge.org] On Behalf Of 
> win32utils-devel at rubyforge.org
> Sent: Wednesday, April 28, 2004 10:43 PM
> To: win32utils-devel at 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



More information about the win32utils-devel mailing list