Re: Died on open command

2003-11-10 Thread R. Joseph Newton
James Edward Gray II wrote: > On Nov 10, 2003, at 4:47 PM, R. Joseph Newton wrote: > > > Look down the thread, and you will find correction from others, also. > > I can > > tell you that I have generated tousands of files in folders reached by > > relative paths, and all I have had to offer Perl w

The File::Spec approach was Re: Died on open command

2003-11-10 Thread drieux
On Monday, Nov 10, 2003, at 14:54 US/Pacific, James Edward Gray II wrote: On Nov 10, 2003, at 4:47 PM, R. Joseph Newton wrote: Look down the thread, and you will find correction from others, also. I can tell you that I have generated tousands of files in folders reached by relative paths, and

Re: Died on open command

2003-11-10 Thread drieux
On Monday, Nov 10, 2003, at 11:03 US/Pacific, Wiggins d Anconia wrote: [..] This is where I very quickly run across the stage yelling "File::Spec->catfile" and then just as abruptly as I entered, exit stage left... Wiggins we were having a Lovely Ideological Struggle between the Forces of Whom

Re: Died on open command

2003-11-10 Thread James Edward Gray II
On Nov 10, 2003, at 4:47 PM, R. Joseph Newton wrote: Look down the thread, and you will find correction from others, also. I can tell you that I have generated tousands of files in folders reached by relative paths, and all I have had to offer Perl was '/'s. It has been working for some time, a

Re: Died on open command

2003-11-10 Thread R. Joseph Newton
James Edward Gray II wrote: > On Nov 10, 2003, at 4:19 PM, R. Joseph Newton wrote: > > > Nope. Not at all. System transparency means not having to concern > > yourself with the system or its quirks, which is what Perl provides in > > re > > file access. Not because the '/' separator is 'nix, bu

Re: Died on open command

2003-11-10 Thread James Edward Gray II
On Nov 10, 2003, at 4:19 PM, R. Joseph Newton wrote: Nope. Not at all. System transparency means not having to concern yourself with the system or its quirks, which is what Perl provides in re file access. Not because the '/' separator is 'nix, but because it is more standard for file systems

Re: Died on open command

2003-11-10 Thread R. Joseph Newton
Chuck Fox wrote: > Just tried on my WindowsXP box. I had to enclose the path in double > quotes. But once I did that, Windows did the right thing, > > dir "\temp" > dir "/temp" > > both give me the temp directory listing. Using single quotes or > backticks does not work. > > Chuck I'll be darn

Re: Died on open command

2003-11-10 Thread R. Joseph Newton
Guay Jean-Sébastien wrote: > > It has nothing to do with what ActiveState did or didn't do. The > > DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the > > path separator however the operating system itself is able to use '/' as > > the path separator. > > Sorry, I just tried it

Re: Died on open command

2003-11-10 Thread R. Joseph Newton
drieux wrote: > john, > > I agree with your basic solution, but since he will > be doing his development in Windows, shouldn't that > be 'file system neutral'? hence not using the unix > separator "/" between the directory component and the filename > component? Nope. Not at all. System transpa

Re: Died on open command

2003-11-10 Thread John W. Krahn
Guay jean-Sébastien wrote: > > > Which version of Perl from ActiveState did this show up in? > > Well, seems ActiveState didn't really have to do anything after all, > according to John W. Krahn. As far as I remember, it's always been like that > in ActiveState Perl. IIRC the ability to use / in

Re: Died on open command

2003-11-10 Thread Wiggins d Anconia
> > On Monday, Nov 10, 2003, at 10:17 US/Pacific, Guay Jean-Sébastien wrote: > [..] > >> I agree with your basic solution, but since he will > >> be doing his development in Windows, shouldn't that > >> be 'file system neutral'? hence not using the unix > >> separator "/" between the directory c

RE: Died on open command

2003-11-10 Thread LoBue, Mark
> -Original Message- > From: Guay Jean-Sébastien > [mailto:[EMAIL PROTECTED] > Sent: Monday, November 10, 2003 10:43 AM > To: 'John W. Krahn'; 'Perl-Beginners' > Subject: RE: Died on open command > > > > It has nothing to do with what

RE: Died on open command

2003-11-10 Thread Guay Jean-Sébastien
> That's exactly what John said. ;) I realized that 5 seconds after I sent the mail... <:-( -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Died on open command

2003-11-10 Thread Chuck Fox
[EMAIL PROTECTED] wrote: It has nothing to do with what ActiveState did or didn't do. The DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the path separator however the operating system itself is able to use '/' as the path separator. Sorry, I just tried it on my machine he

RE: Died on open command

2003-11-10 Thread Guay Jean-Sébastien
> Which version of Perl from ActiveState did this show up in? Well, seems ActiveState didn't really have to do anything after all, according to John W. Krahn. As far as I remember, it's always been like that in ActiveState Perl. But as I said, I still find it great that they didn't do anything to

Re: Died on open command

2003-11-10 Thread James Edward Gray II
On Nov 10, 2003, at 12:39 PM, Guay Jean-Sébastien wrote: It has nothing to do with what ActiveState did or didn't do. The DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the path separator however the operating system itself is able to use '/' as the path separator. Sorry, I ju

RE: Died on open command

2003-11-10 Thread Guay Jean-Sébastien
> It has nothing to do with what ActiveState did or didn't do. The > DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the > path separator however the operating system itself is able to use '/' as > the path separator. Err, just noticed I shouldn't have read so quick... Still,

RE: Died on open command

2003-11-10 Thread Guay Jean-Sébastien
> It has nothing to do with what ActiveState did or didn't do. The > DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the > path separator however the operating system itself is able to use '/' as > the path separator. Sorry, I just tried it on my machine here (NT4), and doing c

Re: Died on open command

2003-11-10 Thread drieux
On Monday, Nov 10, 2003, at 10:17 US/Pacific, Guay Jean-Sébastien wrote: [..] I agree with your basic solution, but since he will be doing his development in Windows, shouldn't that be 'file system neutral'? hence not using the unix separator "/" between the directory component and the filename com

Re: Died on open command

2003-11-10 Thread John W. Krahn
Guay jean-Sébastien wrote: > > > I agree with your basic solution, but since he will > > be doing his development in Windows, shouldn't that > > be 'file system neutral'? hence not using the unix > > separator "/" between the directory component and the filename > > component? > > In a move to si

RE: Died on open command

2003-11-10 Thread Guay Jean-Sébastien
> I agree with your basic solution, but since he will > be doing his development in Windows, shouldn't that > be 'file system neutral'? hence not using the unix > separator "/" between the directory component and the filename > component? In a move to simplify porting of scripts (and save the san

Re: Died on open command

2003-11-10 Thread drieux
On Monday, Nov 10, 2003, at 09:30 US/Pacific, John W. Krahn wrote: Ganesh Shankar wrote: [..] 4) I'm developing on a Windows machine, so I think setting file permissions are unnecessary, right? This problem is described is explained in the documentation for the readdir function. perldoc -f readdir

Re: Died on open command

2003-11-10 Thread John W. Krahn
Ganesh Shankar wrote: > > Hello all, Hello, > I'm starting to learn perl to convert files between different > bioinformatics programs. I'm aware of bioperl but want to learn some > basic perl before using those modules. > > 1) The script is in the same directory as the input folder, so open >