in reply to Too little biggy problems

Thanks guys for the comments.
About my first problem:
-blue_cowdawg: I can't run perl -c on the script. At least I think I can't. I only have FTP access. I'm not using, strict, warnings or diagnostics.
-ChrisR: Thanks, but that's not it. I'm working on a unix box as needed.
-sgifford: What kinda file is that? It's not a perl program, right?
-The Mad Hatter: Again, I only have FTP access to the server so I can't run perl -c (As much as I know).

About my second problem, I'm pretty new with Perl and I guess I was just feeling comfortable without use strict. I guess now as I'm moving forward I find the need to really use it, so I guess I will read the use strict article and docs and get back to you with my second problem (If needed).

Thanks again, and I hope to get more comments about the perl -c thing.

Replies are listed 'Best First'.
Re: Re: Too little biggy problems
by The Mad Hatter (Priest) on Aug 01, 2003 at 19:08 UTC
    sgifford's bit of code was a shell script. Just upload it like you would a Perl script (and put it in the same dir as your download.pl).
[reply]
Re: Re: Too little biggy problems
by blue_cowdawg (Monsignor) on Aug 01, 2003 at 19:10 UTC

        I can't run perl -c on the script. At least I think I can't. I only have FTP access. I'm not using, strict, warnings or diagnostics.

    Run the perl -c on your local machine if you are developing on a linux (or unix) box. (Of course, make sure you have the same Perl modules installed on your local box.

    If there was ever a time for you to use warnings, use strict and use diagnostics, this is one of them.

    Peter @ Berghold . Net

    Sieze the cow! Bite the day!

    Test the code? We don't need to test no stinkin' code! All code posted here is as is where is unless otherwise stated.

    Brewer of Belgian style Ales

[reply]
      The Mad Hatter: Thanks, I'll do that.
      blue_cowdawg: I'm writing on windows, but writing for linux (Well, FreeBSD to be quite honest). I'll try anyway to run perl -c on the script.
      And about the use strict, warnings and diagnostics pragmas, I'll read more about them and do that also.
[reply]
        Did you say that you are writing this script on windows box? Before I thought you said that you weren't. The more correct information you can give us, the more useful help we can give you.
[reply]
        Well, just cahnge your she-bang line. It is probably #/usr/bin/perl

        make it #/usr/bin/perl -W

        and you will get more warnings.

[reply]
        Update: The shell script fixed the problem for me. Cool thing. It gave me a message that I used mkdir() with not enough arguments, which is weird 'cause the MASK argument is optional. I added 0777, and the script works great now. Thanks a lot for that.
        P.S. I used Internet Explorer first to execute the shell script, but the browser wanted to download it. Mozilla executed it good.
        Now I'm gonna read the article about the strict, warnings and diagnostics pragmas and see how it goes on.
        Thanks again guys, you've been very helpful, and I hope in the (not so long) future I will be able to consider myself as a Perl monk (Some boring notes about myself: I'm 19 from Israel, studying Mechanical Engineering in University with a full scholarship from the Israeli Army. Currently working on Windows, but soon moving to Debian GNU/Linux. I started with Perl about 10 months ago. I've taken a few books from my university's library - Programming Perl, Perl Cookbook and Mastering Regular Expressions. My studies pretty much delayed my progression in Perl, but I'm on vacation now so I'm hoping to take some serious progress with my Perl experience. Hey weird thing: I've taken those books 10 months ago, and nobody ordered them every since, they're still at my house...).
        Am I rambling? I'm definitely rambling.
[reply]

In Section Seekers of Perl Wisdom