Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Tue, 12 Nov 2002 22:08:08 +0100
From:	"Gerrit P. Haase" <gp AT familiehaase DOT de>
Organization:	Esse keine toten Tiere
X-Priority:	3 (Normal)
Message-ID:	<8-1996164353.20021112220808@familiehaase.de>
To:	"Soren Andersen" <soren_andersen AT speedymail DOT org>
CC:	cygwin AT cygwin DOT com, module-authors AT perl DOT org
Subject:	Re: Notice of intention to release Perl module specific to Cygwin
In-Reply-To:	<20021112070420.2AC24457D3F@server5.fastmail.fm>
References:	<20021112070420 DOT 2AC24457D3F AT server5 DOT fastmail DOT fm>
MIME-Version:	1.0
X-Sender:	320081107336-0001 AT t-dialin DOT net

Hallo Soren,

Am Dienstag, 12. November 2002 um 08:04 schriebst du:

> [posted today to module-authors AT perl DOT org; posted to cygwin AT cygwin DOT com
> (via Gmane) in order to try to get Cygwin's worthies in the loop].


> Subject: Where it runs or what it Does?? (RFC)
> Date: Mon, 11 Nov 2002 17:56:00 -0500

[...]

> One "trouble" is that conceptually the persons involved with perl on
> Cygwin don't all want any sort of Cygwin:: namespace and don't really
> agree that there's anything unusual about Cygwinperl that differentiates
> it from any generic *nix perl. I know better: on Cygwin, there is always
> going to be more than one canonical-ly-correct way to refer to a file by
> path name (!!): 

[...]

> So my present analysis is that my module belongs in a base namespace of 
> "Filesys::" and maybe could be named "CygwinPaths"? I think it would keep 
> the maintainer of Cygwin Perl happy -- or should -- if named like this.

> What do YOU think?

If you like, why not introduce a namespace CYGWIN:: or Cygwin::, e.g.
there are several modules you didn't mention which are supposed to run
*for* or *with* a specific application like Apache:: or XMail:: or
PLP:: or YAML::, so why not introduce the namespace Cygwin:: (if you
look at Cygwin like just another application).

I would be perfectly happy with a Cygwin:: namespace!


Gerrit
-- 
=^..^=


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -