RE: "Win32::API::Callback::IATPatch" name for DLL/SO hooker for Win32::API
[email protected] (bulk 88)
| Newsgroups | perl.libwin32,perl.modules |
|---|---|
| Message-ID | <[email protected]> |
---------------------------------------- > From: [email protected] > To: [email protected]; [email protected]; [email protected] > Subject: RE: "Win32::API::Callback::IATPatch" name for DLL/SO hooker for Win32::API > Date: Wed, 29 Aug 2012 18:48:34 -0400 > > > > > > To: [email protected]; [email protected]; [email protected] > > Subject: Re: "Win32::API::Callback::IATPatch" name for DLL/SO hooker for Win32::API > > Date: Wed, 29 Aug 2012 16:09:48 +0200 > > From: [email protected] > > > > Hi, > > > > I think it's great that you're trying to push Win32::API forward. > > > > However, having 2 separate Win32::API releases in CPAN > > is not good IMHO, because it creates confusion in users. > > (Which version should I try? What's the advantage of running one or the > > other?) > > > > Do you have your source tree anywhere public? > > > > IIRC I invited you to contribute to the github repository on > > https://github.com/cosimo/perl5-win32-api. > > > > That's still valid. I don't have resources and energy > > to test Win32::API on the set of platforms and compilers > > required for a "quality" release anymore, but if we > > try to converge towards one single tree/release, then > > we can get help from others too. > > > > Opinions? > > > > -- > > Cosimo > > My code lives at https://github.com/bulk88/perl5-win32-api . I absolutely would like to merge it in/make it the official Win32::API on CPAN, tell me your plan. I haven't heard from you since my last post a month ago. I've submitted a pull request ( https://github.com/cosimo/perl5-win32-api/pulls?direction=desc&page=1&sort=created&state=open ) to you github a month ago, but there was no response to date. I am requesting that you either incorporate my changes and make a new CPAN release, or give me COMAINT on Win32::API (PAUSE ID is BULKDD). I am also forwarding this message to [email protected].