Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <42089E17.8070000@familiehaase.de> Date: Tue, 08 Feb 2005 12:10:15 +0100 From: "Gerrit P. Haase" Organization: Esse keine toten Tiere User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.3) Gecko/20040910 MIME-Version: 1.0 To: Yitzchak Scott-Thoennes CC: Reini Urban , cygwin@cygwin.com, libwin32@perl.org Subject: Re: perl winpid? References: <42065552.4050504@x-ray.at> <42076A6C.90404@x-ray.at> <20050208063131.GA3096@efn.org> In-Reply-To: <20050208063131.GA3096@efn.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Yitzchak Scott-Thoennes wrote: > On Mon, Feb 07, 2005 at 02:17:32PM +0100, Reini Urban wrote: > >>Igor Pechtchanski schrieb: >>>On Sun, 6 Feb 2005, Reini Urban wrote: >>>>I feel quite stupid now, but found nothing simple. >>>>How to get the winpid from the current process in cygwin's perl? >>We will check out there where this cygwin specific functionality >>will go to. >>Win32::Process::CygwinToWin32ProcessID() is my suggestion. > I'd rather see them in the Proc:: namespace, and I think it would make > sense to put them in perl's cygwin.c itself, if Gerrit is willing to > release yet another perl-5.8.6. If this sounds OK, I'll come up with > a patch. I have no problem with another release. And I agree that such important functions should go inside perl. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/