Hi all, I was thinking that maybe we should separate the Daemon class into its own package. Partly because the service.c file is getting a little messy and partly because it seems logical to separate the service control side from the service implementation side. Thus, you would have: require "win32/service" require "win32/daemon" Also, I noticed that the current Daemon class uses the 1.8 allocation framework. Do we want to scrap support for 1.6.x? If so, should we change the Service class to use the 1.8 allocation framework? Regards, Dan
> -----Original Message----- > From: win32utils-devel-bounces@rubyforge.org > [mailto:win32utils-devel-bounces@rubyforge.org] On Behalf Of > win32utils-devel@rubyforge.org > Sent: Tuesday, January 27, 2004 12:38 PM > To: win32utils-devel@rubyforge.org > Subject: [Win32utils-devel] daemon class > > > Hi all, > > I was thinking that maybe we should separate the Daemon class > into its own package. Partly because the service.c file is > getting a little messy and partly because it seems logical to > separate the service control side from the service > implementation side. Thus, you would > have: > > require "win32/service" > require "win32/daemon"Oh, I just realized that Daemon is a subclass of Service. Well, we can still separate them into separate files, can''t we? Dan
Hi,> > > -----Original Message----- > > From: win32utils-devel-bounces@rubyforge.org > > [mailto:win32utils-devel-bounces@rubyforge.org] On Behalf Of > > win32utils-devel@rubyforge.org > > Sent: Tuesday, January 27, 2004 12:38 PM > > To: win32utils-devel@rubyforge.org > > Subject: [Win32utils-devel] daemon class > > > > > > Hi all, > > > > I was thinking that maybe we should separate the Daemon class > > into its own package. Partly because the service.c file is > > getting a little messy and partly because it seems logical to > > separate the service control side from the service > > implementation side. Thus, you would > > have: > > > > require "win32/service" > > require "win32/daemon" > > Oh, I just realized that Daemon is a subclass of Service. Well, we can > still separate them into separate files, can''t we? > > Dan >I know the source code is a little messy:-) Let''s separate it into service.c and daemon.c file. But I think it''s better to build one library file service.so I don''t care which framework is used. I think that the most ruby users on windows platform use Ruby 1.8.x Or at least not too difficult to upgrade to Ruby 1.8.x for the precious Win32-Utils :-) Regards, Park Heesob --MIME Multi-part separator--