From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27775 invoked by alias); 19 Feb 2004 22:24:53 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 18600 invoked from network); 19 Feb 2004 22:01:03 -0000 Received: from unknown (HELO soulshock.mail.pas.earthlink.net) (207.217.120.130) by sources.redhat.com with SMTP; 19 Feb 2004 22:00:59 -0000 Received: from hawk.mail.pas.earthlink.net (hawk.mail.pas.earthlink.net [207.217.120.22]) by soulshock.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id i1JK1Z913881 for ; Thu, 19 Feb 2004 12:01:35 -0800 (PST) Received: from 1cust164.tnt12.krk1.da.uu.net ([67.250.176.164] helo=efn.org) by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1AtuM9-0006m5-00 for cygwin@cygwin.com; Thu, 19 Feb 2004 12:01:10 -0800 Received: by efn.org (sSMTP sendmail emulation); Thu, 19 Feb 2004 12:01:08 -0800 Date: Thu, 19 Feb 2004 23:11:00 -0000 From: Yitzchak Scott-Thoennes To: cygwin@cygwin.com Subject: Re: [Fwd: Bug: Perl:IsWinNT undefined & RFE, only use "/" in reg values, not names..?] Message-ID: <20040219200107.GA1344@efn.org> References: <40350E21.9010204@tlinx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40350E21.9010204@tlinx.org> User-Agent: Mutt/1.4i Organization: bs"d X-IsSubscribed: yes X-SW-Source: 2004-02/txt/msg01010.txt.bz2 On Thu, Feb 19, 2004 at 11:27:29AM -0800, linda w wrote: > What features does one get with a unix perl over a perl built where > "WinNT" is > defined as true or false? Many (most? all?) of the Win32 calls are > available > in the Cygwin environment, why not compile the perl as a mixed breed > perl that > defines WinNT? If possible, please shorten your lines. > What is lost by allowing Perl to make libwin32 calls. > > If Cygwin is supposed to enable me to run my utils and scripts from bash or > cnd.exe, then why should perl be different? What do I lose by defining > -MWin32 > in the PERL5OPS?, or put another way, why isn't it on and present all > the time? Because the perl-libwin32 package was released a little over 3 weeks ago. Allow some time, please. On the win32-perl/ActiveState side, the stuff in our package is divided into two places, the perl core, and the libwin32 CPAN distribution. -MWin32CORE will get you what is in the perl core for non-cygwin perl's. The need for that should go away at some point. Code using other Win32:: parts should already have "use Win32". Note that cygwin runs not just on WinNT and derivitaves; you can expect Win32::IsWinNT to return false for Win9x, just as it does with ActiveState (IIRC). > Besides, it seems, that the cpan modules for perl can't be for active state > perl since they have their own package manager -- but are for the > floundering > win32-perl that is mostly eclipsed by active state's perl and cygwin's > perl. As far as I know, they are usable with ActiveState (for XS modules assuming you have the same compilation tools ActiveState uses). That lanman thing seems to be an abberation, in that it isn't set up like a real perl module. > It seems cyg_win_ was designed to add POSIX and unix compatibility and > functionality to the _Win_ environment with the intent of making things > _easier_ (Easy is good -- not everyone can be a master of every technology). > So why not make things easier for perl scripters as well by starting with > a perl that is unix (works with cpan, handles paths with "//", "/") and > win (paths handle "\\", ":" and "\\\\" and define WinNT) compatible? > > Is there some fundamental reason why they can't both be present in perl? In making POSIX-like paths work in a drive-letter world, you can't have everything. What is it exactly that you would like that you see as missing? -- 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/