Perl script - Linux to Windows

[guru]

HI

I have written a script which runs successfully in Linux. But When I
took same script and ran in Windows it is failing.

I tried to figure out if there any problem with following,

1. Paths handling --> Wheter this should be handled.
I came to know that perl will handle path structure depending
on the OS.
2. Configuration setting.

Any other parameters I need to look while porting to Windows.

Thanks & Regards
Gururaja

 

[Noway]

HI

I have written a script which runs successfully in Linux. But When I
took same script and ran in Windows it is failing.

How do you know that it fails under win?

 

[Gunnar Hjalmarsson]

HI

I have written a script which runs successfully in Linux. But When I
took same script and ran in Windows it is failing.

I tried to figure out if there any problem with following,

1. Paths handling --> Wheter this should be handled.
I came to know that perl will handle path structure depending
on the OS.
2. Configuration setting.

Any other parameters I need to look while porting to Windows.

There is a bug at line 126 of the script.

 

[guru]

There is a bug at line 126 of the script.

Thanks Gunnar. I got the answer. This is a general question that I
asked. While porting I faced some problem with path and configuration.
So I asked any other I need to consider.

 

[guru]

How do you know that it fails under win?

Scenario is fun1.pl is calling fun2.pl, while passing it is passing
list of files too.
In fun2.pl i am failing to read those file.

What I got is if file is passed like 'filename1' then fun2.pl will
fail to open it, so I passed without '' and it worked.

 

[RedGrittyBrick]

Scenario is fun1.pl is calling fun2.pl,

Presumably using system() or backticks.

while passing it is passing
list of files too.
In fun2.pl i am failing to read those file.

What I got is if file is passed like 'filename1' then fun2.pl will
fail to open it, so I passed without '' and it worked.

Sounds fragile, maybe you should convert fun2.pl to a module fun2.pm so
that you are not dependant on the quirks of shells in various operating
systems.

 

[Gunnar Hjalmarsson]

Thanks Gunnar. I got the answer.
Good.

This is a general question that I
asked. While porting I faced some problem with path and configuration.
So I asked any other I need to consider.

Your problem was not general at all. Next time you ask a question,
please make it easy to help by following the posting guidelines for this
group.

http://www.rehabitation.com/clpmisc/clpmisc_guidelines.html

 

[Jürgen Exner]

I have written a script which runs successfully in Linux. But When I
took same script and ran in Windows it is failing.

I tried to figure out if there any problem with following,

1. Paths handling --> Wheter this should be handled.
I came to know that perl will handle path structure depending
on the OS.

Depends on what you mean. Obviously Windows doesn't have e.g. an
/etc/proc and neither named pipes or sockets as part of the file system
just as you need to consider the concept of drives.

2. Configuration setting.

Again, depends on what you mean.

Any other parameters I need to look while porting to Windows.

Did you read 'perldoc perlport'?

jue