The point has been made, and not yet refuted, that the best place to add this value would be as a File::Spec::Cygwin module. I happen to agree with that and would like to hear the counter-argument before a new namespace is added.

-dsb

At 04:23 AM 11/13/2002 +0000, Soren A wrote:
On Tue, 12 Nov 2002 21:08:08 GMT, [EMAIL PROTECTED] (Gerrit P. Haase)
wrote in news:8-1996164353.20021112220808@;familiehaase.de:

> 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!
>
>

Oh, OK, Gerrit. I may have interpolated incorrectly or too much, from
some past discussions. But I think barring any very persuasive arguments
to the contrary (that would have to be offered mighty soon, now), that
I'll be going with the Filesys::CygwinPaths namespace for this module. I
tend not to want to look at Cygwin as an application, but rather I want
to look at it like an environment that supports doing things in a
certain (POSIX-ish) way.

And I have in fact uploaded (not registered the namespace yet of course)
already. If you are interested in trying to build and check out the
module, Gerrit (or other readers who are Cygwin users, ... who might
thereby serve this project [which IS worthy!] as beta testers) then you
may get the targzball in the CPAN directory:

  http://www.cpan.org/modules/by-
authors/id/S/SO/SOMIAN/experimental/unregistered/

Thanks for your reply.

   Soren A


--
  conway: unit of mind expansion.
One Conway == ~20 lines of Perl code found in
$CPAN/authors/id/D/DC/DCONWAY, which gives the
sensation of your brain being wrapped around a
brick, with kiwi juice squeezed on top.
        -- Ziggy (via Schwern)


Reply via email to