Benjamin Scott wrote:
> > (Of course, at least you *can* move a perl program to win32. Ever tried
> > porting a csh program to win32? ;)
>
> With a good POSIX environment, like CygWin for example, I imagine it
> wouldn't be that hard.
Now, see, this is what is confusing to me... In a post earlier today,
you were saying that you couln't port to a win32 platform because of
missing commands like grep, cat, etc. Now you are saying that with
CygWin32 it shouldn't be that hard. Well, of course it shouldn't, since
all of those commands exist in that environment. Which brings me to my
second point of confusion. You said :
> No program exists in a vacuum. It's nice to blame
> portability on the environment, but if your program
> doesn't interact with the environment in anyway at all,
> why are you running it? :-)
Isn't this fairly contradictory? You're talking about installing a POSIX
environment on a Win32 system to aid portability. Therefore, you aren't
porting the program, but rather, the environment. So, the question
shouldn't be why use the tool, but instead, why use the environment?
Kenny
PS I won't claim to be a Perl god, since I'm not. I'm just confused and
tired ;-)
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
