[25573] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 7817 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Feb 23 09:05:59 2005

Date: Wed, 23 Feb 2005 06:05:40 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Wed, 23 Feb 2005     Volume: 10 Number: 7817

Today's topics:
    Re: Annoying Problem with a Basic Perl app and XP Pro <mark.clements@kcl.ac.uk>
    Re: Annoying Problem with a Basic Perl app and XP Pro <1usa@llenroc.ude.invalid>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <1usa@llenroc.ude.invalid>
    Re: Annoying Problem with a Basic Perl app and XP Pro <1usa@llenroc.ude.invalid>
    Re: Annoying Problem with a Basic Perl app and XP Pro (Anno Siegel)
    Re: Annoying Problem with a Basic Perl app and XP Pro <wyzelli@yahoo.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <1usa@llenroc.ude.invalid>
    Re: Annoying Problem with a Basic Perl app and XP Pro <bastard@uni-koblenz.de>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <bastard@uni-koblenz.de>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro <mark.clements@kcl.ac.uk>
    Re: Annoying Problem with a Basic Perl app and XP Pro <jpmythic@ntlworld.com>
    Re: Annoying Problem with a Basic Perl app and XP Pro (Anno Siegel)
    Re: Annoying Problem with a Basic Perl app and XP Pro <bastard@uni-koblenz.de>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Wed, 23 Feb 2005 12:05:03 +0100
From: Mark Clements <mark.clements@kcl.ac.uk>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <421c6363$1@news.kcl.ac.uk>

arek wrote:
> Also, it WILL fail if the following Files do NOT exist in the same Dir:
> 
> movfiles.txt
> primary.inf
> 

Not really a Perl answer this, but have you considered using something 
like lftp?
May do what you need without having to fiddle around with this script. 
Note you may have to run it under cygwin.

Mark


------------------------------

Date: Wed, 23 Feb 2005 11:14:03 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <Xns96063F6BEFC83asu1cornelledu@127.0.0.1>

"arek" <jpmythic@ntlworld.com> wrote in
news:1109153296.612715.40020@o13g2000cwo.googlegroups.com: 

> Actually those were caused by Wrapping during post...
> It DOES compile without errors if you correct the Wrapping in the
> Post. 

Sigh. From your original post:

> sub main_transfer {
>      # Only have something to do if there is a list of new files.
>         if (-f "$mov_file")
>      {
>           my $result;
> 
> ($primary_web, $primary_directory, $primary_username,
> $primary_password) = parse_information_file $primary_info);

That has nothing whatsoever to do with wrapping as far as I can see.

> So a more usefull reply would be appreciated...

A more readable post with code that is short, to the point and easily
runnable also would have been appreciated. 
 
> Not trying to be nasty, but those Compile Errors are not Code issues,
> just failure to look at the Code before just cutting and pasting it 
> and running it ...

I see. It is my fault that you posted code that does not compile and
gives warnings. 

Please read the posting guidelines. They contain valuable information on
how to help others help you. Posting hundreds of lines of code that
contains errors and uses many many global variables will not help you
get help. 

Let's go over what you posted:

> use English;

Why?

> use strict;

Missing

use warnings;

> use Time::Local;
> use Net::FTP;
> 
> my $mov_file;               # List of Files to transfer
> my $log_file;               # Log file to store information
> my $primary_info;          # WebSite connection information

1. You should declare variables in the smallest applicable scope. 

2. If you did that, you would not have to put meaningless comments in
the right margin. 

As it is, trying to comprehend your code requires remembering the state
of 14 different variables some of which are aggregates. Yuck! 

> do {
> 
>      sleep $time_period;     # Sleep until next transfer time
>      main_transfer();     # Transfer Status files
> 
> } while (1);               # Forever loop as XP Scheduler SUCKS!!

Whatever you say.

> sub main_transfer {

This routine does not seem to be re-entrant. 

>      # Only have something to do if there is a list of new files.
>         if (-f "$mov_file")

Useless use of quotes.

perldoc -q always

 What's wrong with always quoting "$vars"?

>      {
>           my $result;
> 
> ($primary_web, $primary_directory, $primary_username,
> $primary_password) = parse_information_file $primary_info);

Syntax error.

> 
>           open FILES, "$mov_file" || die write_log("Unable to open
>           file $mov_file");


Precedence problem.

    	    open FILES, $mov_file or die $!;

or

    	    open(FILES, $mov_file) || die $!;

Why do you ignore $!?

> ------ sub put_files {
>     my $hostname  = shift @_;
>     my $directory = shift @_;
>     my $username  = shift @_;
>     my $password  = shift @_;
>     my @files     = @_;
>     my $n_files;
>     my $file;
>     my $ret;
>     my $ftp;
>      my @transfers;
>      my $dotransfers;

Again, you should declare variables in the smallest applicable scope. If
you are going to pass this many arguments to a function, think about
using a hash of parameters. 

>     $n_files = @files;

Hmmmm ....

>     $dotransfers = 0;
> 
>     clear_ftp();

If you declared variables in the smallest applicable scope, you would
not need these contraptions. All clear_ftp is doing is 

@ftp_commands = ();

But your reader has to jump back and forth to see that.

And I am exhausted from doing just that.
Please read the posting guidelines and follow them.

Sinan.


------------------------------

Date: 23 Feb 2005 03:15:21 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109157321.368097.323690@z14g2000cwz.googlegroups.com>

My bad,  must have messed that up when I was cut and pasting it...
As for it compiling without errors and then it failing on the posted
version, generally points to a
post error....

I had attempted to clean it up during posting, and accidently clipped
that one...  :(
So again, little bugs like that generally point to a Post error, not a
Code error...

Simply, It won't COMPILE on mine either straight from the Post, EVEN I
would have noticed that
glitch and not pointed it out as a program error but a posting error...
I didn't bother looking at the Posted code as I expected the word
wrapping and
immediately "Identified" that with the [ syntax error {and} ] in the
first reply.

Which means if I posted any suggestions i would have mentioned it as a
possible Post error, not a code error.


I DID forget to turn on [ -w ],  my error there,  but the Strict tends
to avoid alot of problems which is why I used it.
As for the Scalar,  Again, I said I am new to Perl and had taken a
Simple Original App (AutoFtp.pl) and modified
it to do what I needed, so the Scalar was an error in the Original that
I did not recognise as an error.

Thx for spotting the actual cause of the POST error...

Now that we have Post errors out of the Way...

Would this Scalar issue Affect ONLY XP Pro and NOT XP Home???
That is the big question...  The basics of both versions of XP should
not cause it to fail on one and work on another
as far as I can see...


I'll be testing it with [ -w ] on and modifing it as posted before...
But I highly suspect I will be getting the same issue...
Simply put, IF the scalar issue is a Problem, it shouldn't work at
all..

And it IS a :

"whatever code _IS_ working on the XP Home PC."

Issue as I stated in the very begining...
The Code DOES work on XP Home....
The Code DOESN'T work on XP Pro...

Once past the simple Post errors and compiled, you should find it
works..
Or if it doesn't and Your using XP Pro, then you are having the same
problem I am.



------------------------------

Date: Wed, 23 Feb 2005 11:15:33 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <Xns96063FACE1AB5asu1cornelledu@127.0.0.1>

"Peter Wyzl" <wyzelli@yahoo.com> wrote in
news:niZSd.172389$K7.93343@news-server.bigpond.net.au: 

> "arek" <jpmythic@ntlworld.com> wrote in message 
> news:1109148706.355661.207320@z14g2000cwz.googlegroups.com...
>: New to perl, but not new to C++.  I wanted a simple and efficeint app
>: to update some small pages to a remote website.  I had used a old
>: perl app in Linux before called AutoFtp.pl, so I looked for it and
>: did some modifications.  It was working fine on my Test workstations,
>: (XP Home), so I figured I had it licked and moved to the Main Server,
>: (XP Pro). 
>:
>: Now I am getting nowhere, Literally.  The application runs, but does
>: absolutely nothing....
> 
> You are aware that the first thing the program does (after fixing the
> main errors, see Sinan and my other post) is sleep for 30 minutes?

:))

I completely missed that!

Sinan.


------------------------------

Date: Wed, 23 Feb 2005 11:19:31 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <Xns9606405905C07asu1cornelledu@127.0.0.1>

"arek" <jpmythic@ntlworld.com> wrote in news:1109157321.368097.323690
@z14g2000cwz.googlegroups.com:

> My bad,  must have messed that up when I was cut and pasting it...
> As for it compiling without errors and then it failing on the posted
> version, generally points to a post error ...

At this point, you need to go read the posting guidelines and come back 
only when you have understood their value. 

> Simply, It won't COMPILE on mine either straight from the Post, EVEN I
> would have noticed that glitch and not pointed it out as a program
> error but a posting error...

So, it is still my fault? If there is a discrepancy between code you post 
and code that is on your computer, how can we figure out if the errors and 
warnings pointed out by perl are the *only* discrepancies?

*PLONK*

Sinan


------------------------------

Date: 23 Feb 2005 11:28:01 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <cvhpc1$atk$1@mamenchi.zrz.TU-Berlin.DE>

arek <jpmythic@ntlworld.com> wrote in comp.lang.perl.misc:

Give an attribution and some context when you post.  This was in reply to
A. Sinan Unur pointing out syntax errors.

> Actually those were caused by Wrapping during post...

Some where.  Others weren't.

It is your job to present code in a form that we can readily run and debug.
Dumping 250+ lines of wrap-damaged code to the newsgroup won't do.

> It DOES compile without errors if you correct the Wrapping in the Post.
>
> As I said, "It Compiles without Errors AND works on the XP Home boxes"

No, it doesn't.  Explain how the syntax error in

    ($primary_web, $primary_directory, $primary_username,
    $primary_password) = parse_information_file $primary_info);

is brought about by line wrapping.

> So a more usefull reply would be appreciated...

A more useful problem presentation would be a first step.

> Not trying to be nasty, but those Compile Errors are not Code issues,
> just failure to
> look at the Code before just cutting and pasting it and running it..

Did you even check the errors Sinan pointed out?

> I am quite used to
> watching out for Wrapping problems from Web Based copys...

How nice.  How about developing a habit of reading *all* of a post
before replying?

Anno


------------------------------

Date: Wed, 23 Feb 2005 11:26:11 GMT
From: "Peter Wyzl" <wyzelli@yahoo.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <nLZSd.172443$K7.8651@news-server.bigpond.net.au>

"arek" <jpmythic@ntlworld.com> wrote in message 
news:1109157321.368097.323690@z14g2000cwz.googlegroups.com...
: My bad,  must have messed that up when I was cut and pasting it...
: As for it compiling without errors and then it failing on the posted
: version, generally points to a
: post error....


<snip>


: Once past the simple Post errors and compiled, you should find it
: works..
: Or if it doesn't and Your using XP Pro, then you are having the same
: problem I am.


Well, for me it sleeps for 30 minutes, and I got bored... :)

Maybe you have a firewall problem???  Check that...

Seriously, there are lots of other problems here, try to follow some of the 
suggestions in Sinan's second post.

P
-- 
print "Just another Perl Hacker";




------------------------------

Date: 23 Feb 2005 03:38:15 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109158695.245931.129820@o13g2000cwo.googlegroups.com>

Well....  I can see that I got nailed hard...

To iterate...  I am learning Perl from previous posted example Apps...
90% of this code is from the Original with little to No modifications
by me...

Now if we ignore all the hollering and look at it:

1: Yes, some of this code is really ugly,  especially as I am learning
from what OTHERS have posted.
2: Yes.. I messed up the post, BUT even I with only 3 days of Perl
experience I easily spotted Typos from posting.
3: The only useful post was the reminder to use  [ use warnings ]

Guess what?  That found the Issue,  AND IT IS an ISSUE between XP Home
and XP Pro...!!!!
Still works fine on XP Home, BUT NOW reports the Error on XP Pro...

The REAL Cause of the Problem:
  Use of Unitialized value in subtraction <-> at Line 135

SOOOooo  with all your gripes over simple errors in the post Nobody
bothered to look at where it actually
had a problem:

[CODE Snippet]   (Other boards have a better system to post code
snippets that don't wrap)

# The Job runs at a PreSet time period

$file_time = (stat($file))[9];
$system = time;
$system -= $file_time;

[CODE Snippet]

Here as you can see I decided there was no need to OPEN the file just
to get the modification date
as it seemed to show you didn't NEED to open it to access the file
attributes...

Now yes,  IF I had used the [ use warnings ] I would have fixed this on
my OWN without ever having
talked to you ALL!

But by talking to you, we NOW know XP Pro does NOT allow access to the
Atrributes without Opening the
file First!  How many of you are aware of this difference between XP
home and pro????

Mind you,  It was ME not you that determined the Cause...

And yes, the code is NOT the sweetest thing out there...  My C++ is
beautiful compared to my Perl,
but then again, I have been working with C++ for years and Perl for
just a few Days....

This is supposed to be a HELP forum not a Bitch at the new guy forum...
Yet I still was nice enough to pass on Information you all seem to be
unaware of!



------------------------------

Date: 23 Feb 2005 03:40:55 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109158855.718500.172280@o13g2000cwo.googlegroups.com>

One Note to other users of Perl:

XP Pro is far more strict in access to files and other things then XP
Home...
Be careful when writing apps and testing them on one then trying to run
them on another

What may run without problems on XP Home, may not necessarily run on XP
Pro.

The actual problem was in Accessing File Attributes in XP Pro...
XP Pro requires Opening the File Before attempting to read Attributes..

I don't think I will be back..



------------------------------

Date: 23 Feb 2005 03:44:08 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109159048.014431.59490@g14g2000cwa.googlegroups.com>

If your [Exhausted] from reading less then 2 pages of code,
How the heck can you debug 10K lines worth of Code?
I work with programs that contain more then 500 seperate documents
(each a C++ .h or .cc file)
and your complaing about less then TWO pages Heavily Commented??

Sheesh!



------------------------------

Date: 23 Feb 2005 03:55:48 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109159748.222298.281910@g14g2000cwa.googlegroups.com>

Again...  Yes I am aware of That... I added that for the specific
reason
of getting a constant running app that checks the files at a Specified
time...
Try getting Windows Scheduler to run an App every hr on the hr... It's
a pain..

And as far as sitting there waiting a Half Hour for it to do
something...
*Laughs*,  even I would'nt run it like that for testing unless I was at
the final stage...

I posted the full code as it is suppose to run...
You simply CHANGE the time period,  which is ALSO why I made it a
Global, as it
is used for more then one thing and If I need to Change that period, I
can CHANGE it
at ONE spot, instead of having to make sure I caught All occurances of
it!

Sheesh.



------------------------------

Date: Wed, 23 Feb 2005 11:59:53 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <Xns960647313C20Casu1cornelledu@127.0.0.1>

"arek" <jpmythic@ntlworld.com> wrote in
news:1109158695.245931.129820@o13g2000cwo.googlegroups.com: 

> Guess what?  That found the Issue,  AND IT IS an ISSUE between XP Home
> and XP Pro...!!!!

I am glad I post-dated my *PLONK*.

I am only writing this for the benefit of others as you, based on your
ignorance, are intent on misleading others. 

> [CODE Snippet]   (Other boards have a better system to post code

This is UseNet, not a board.

> $file_time = (stat($file))[9];

 ...

> Here as you can see I decided there was no need to OPEN the file just
> to get the modification date

 ...

> But by talking to you, we NOW know XP Pro does NOT allow access to the
> Atrributes without Opening the file First!  How many of you are aware 
> of this difference between XP home and pro????
> 
> Mind you,  It was ME not you that determined the Cause...

It doesn't change the fact that you are wrong.

I have never used XP Home. Currently running XP Pro SP2:

D:\Home\asu1\UseNet\clpmisc> cat f.pl
use strict;
use warnings;

print "@{[ stat shift ]}\n";
__END__

D:\Home\asu1\UseNet\clpmisc> f 30.gif
3 0 33206 1 0 0 3 465 1106542800 1106426038 1106609944

Clearly, no requirement to open the file first to be able to stat it.

Your problem lies elsewhere.

My comment regarding your use of open in
<news:Xns96063F6BEFC83asu1cornelledu@127.0.0.1> might help. Otherwise
you are on your own because your code is too hard to read. 

If you do try to exercise good programming discipline and put some work
into following the suggestions in the guidelines, you will be able to
solve your problem. 

> Yet I still was nice enough to pass on Information you all
> seem to be unaware of!

Everyone, I promise this is my last post in this thread. I just posted 
because there aren't too many people who use XP here and the troll's 
wrong statement regarding XP and the stat function had to be corrected.

Sinan.


------------------------------

Date: Wed, 23 Feb 2005 14:08:04 +0100
From: Dimitri Papoutsis <bastard@uni-koblenz.de>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <cvhreb$p0q$1@news.uni-koblenz.de>

A. Sinan Unur wrote:

> "arek" <jpmythic@ntlworld.com> wrote in news:1109157321.368097.323690
> @z14g2000cwz.googlegroups.com:
> 
>> My bad,  must have messed that up when I was cut and pasting it...
>> As for it compiling without errors and then it failing on the posted
>> version, generally points to a post error ...
> 
> At this point, you need to go read the posting guidelines and come back
> only when you have understood their value.

Yes Daddy, thx for that useful advice...
 
>> Simply, It won't COMPILE on mine either straight from the Post, EVEN I
>> would have noticed that glitch and not pointed it out as a program
>> error but a posting error...
 
> So, it is still my fault? If there is a discrepancy between code you post
> and code that is on your computer, how can we figure out if the errors and
> warnings pointed out by perl are the *only* discrepancies?

Now some advice for you, son:
If you want to help someone DO it... if not, then DO NOT mention the
accordant thread. I had a look on your pseudo-trial to response "arek" in a
helpful way. But all i saw were some "Style-Guidelines"... somehow a
statement about "bad coding style". What i didn't see was a "fair" way of
treating a clearly presented problem in addition to the complete code.

If you comply, that the code does not compile, i have to suggest that you
are not able to read "Program-Codes" on their semantical level. So, aren't
you more than a better syntax-and-styleguide-parser ?

My main advice for you, son: Don't bother, if you don't feel like helping...
Just stop reading a thread ... but maybe, ... your problem ist deeper. I
won't presume to assume that you got personal problems, but i will give you
some further questions to take with you on your way of life:

1. Have you problems with your friends, or your life-partner ?
2. Didn't your parents give you enough love ?
3. Maybe you've been violated or raped as a young boy ?
4. What about your sexuality ? Have you sexuality ?
5. Aren't you well payed for your job ?
 => What are the roots of your inner imbalance and social incompetence ?

And as i said  i just ask you, because i wanna help you, son... And please,
don't think about answering these questions to me, boy, these are YOUR
questions... only for you. So , kid, hope you will integrate the following
to terms to your vocabulary and your "basic understanding of solving
problems" : "inner (im)balance" and "social (in)competence".

Thank you for reading this, son
i love you, too

kisses
daddy



------------------------------

Date: 23 Feb 2005 04:11:01 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109160661.118194.198120@g14g2000cwa.googlegroups.com>

hmm... Yes I did read the post... Yes I did spot my Mistake
But guess what?  Can't edit the post to correct it...

And yes I checked his errors out...

As far as that goes, did ANYBODy even bother to Read what the Code was
doing?
If they had, they would have noticed right away, (As it IS heavily
commented), that it SLEEPS
for the first 30 minutes...

Any body halfway decent at coding would have easily seen the need to
change that to a
shorter period to do testing...

And IF I could Edit my posts I would have corrected the Errors in the
original,
BUT as everyone seemed more interested in griping about 3 and I DO MEAN
[3] small
glitches in the Original code posted, 2 caused by wrapping, 1 by my
trying to make it
more readilable,  the only problem with that is this Boards posting
system...

If people spent more time helping rather then groaning about simple
typos and a
SMALL error in posted code... I mean heck, what do you do if someone
sends you
code to work on and they screwed up your Name?  Send it back?

If you were Really good at Coding, that SMALL error shouldn't have even
made you blink!
ONE missing [ ( ] and everyone's bitching... Honestly, can you call
that UnReadable and
UnWorkable code?

Oy..



------------------------------

Date: Wed, 23 Feb 2005 14:26:46 +0100
From: Dimitri Papoutsis <bastard@uni-koblenz.de>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <cvhshd$p0q$3@news.uni-koblenz.de>

arek wrote:

> hmm... Yes I did read the post... Yes I did spot my Mistake
> But guess what?  Can't edit the post to correct it...
> 
> And yes I checked his errors out...
> 
> As far as that goes, did ANYBODy even bother to Read what the Code was
> doing?
> If they had, they would have noticed right away, (As it IS heavily
> commented), that it SLEEPS
> for the first 30 minutes...
> 
> Any body halfway decent at coding would have easily seen the need to
> change that to a
> shorter period to do testing...
> 
> And IF I could Edit my posts I would have corrected the Errors in the
> original,
> BUT as everyone seemed more interested in griping about 3 and I DO MEAN
> [3] small
> glitches in the Original code posted, 2 caused by wrapping, 1 by my
> trying to make it
> more readilable,  the only problem with that is this Boards posting
> system...
> 
> If people spent more time helping rather then groaning about simple
> typos and a
> SMALL error in posted code... I mean heck, what do you do if someone
> sends you
> code to work on and they screwed up your Name?  Send it back?
> 
> If you were Really good at Coding, that SMALL error shouldn't have even
> made you blink!
> ONE missing [ ( ] and everyone's bitching... Honestly, can you call
> that UnReadable and
> UnWorkable code?
> 

=> FullACK

If anyone would have really been intrested in helping, he would have asked
you for mailing him your code in respect to the avoidance of
Posting-Errors.
How about mailing me your code, maybe i can help, it's my free day today.

bye
Dimi



------------------------------

Date: 23 Feb 2005 04:33:01 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109161981.673037.61400@g14g2000cwa.googlegroups.com>

Ahhh, here we have the Great perls of Wisdom.....

Never used XP Home eh? then how can you effectivley Answer my
problem/question?
Spent more time complaining about my coding style then trying to
help...

So...  XP Pro doesn't have a Problem Stating a file?  Are you 100%
sure?
Because in this case it is....  So according to you, If it works on
yours, then theirs no problem,
Real help there you are...

Not familiar with the fact that some systems could have Fat32 OR NTFS
filesystems eh?
What works on Fat32 may not work on NTFS...  So just stating: "It works
on mine", is not in itself
a correct statement...

So I am a troll eh? Well actually yes, some days I am when I get
useless Complaints about
coding style that has nothing to do with the actual problem....

One missing [ ( ] and I just can't code worth crap eh? And that makes
me a Troll as well I guess.

Man I guess I am just having a bad day today.  Figured I'd seek some
help from so called Gurus
who spend more time complaining about a Typo in the Post then the
actual issue I'm having,
so I guess if I toss it back at ya it makes me a Troll....



------------------------------

Date: 23 Feb 2005 04:44:47 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109162687.312226.55270@g14g2000cwa.googlegroups.com>

Actually I had thought about using a Tftp, but it's not very secure and
requires
loading both the Server AND the Client.  Don't need the server and was
looking
for something Light that was easy to modify for my own needs if they
ever changed..

And yes, this setup is not that Secure either, but at least it doesn't
create a Server as well,
need all the power for the Primary application that runs on the Server
as it is.

Had already used the Original AutoFtp.pl almost a year ago on one of my
Linux boxes
so I figured shouldn't be too much trouble to Mod it to run on XP
Pro....  
(Murphy's Law takes affect here).



------------------------------

Date: Wed, 23 Feb 2005 13:46:09 +0100
From: Mark Clements <mark.clements@kcl.ac.uk>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <421c7b15$1@news.kcl.ac.uk>

arek wrote:
> Actually I had thought about using a Tftp, but it's not very secure and
> requires
lftp ie LFTP. I suspect that I am the only person still listening.


------------------------------

Date: 23 Feb 2005 04:56:13 -0800
From: "arek" <jpmythic@ntlworld.com>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <1109163373.156013.163120@l41g2000cwc.googlegroups.com>

Quote
"
Seriously, there are lots of other problems here, try to follow some of
the
suggestions in Sinan's second post.
"
UnQuote

If there are so many Problems here.... Then HOW does it work on the XP
Home box???
If you have XP Home and can compile it and it DOESN'T work, then yes,
it has problems,
Yet you yourself stated:

Quote
"Well, for me it sleeps for 30 minutes, and I got bored... :) "
UnQuote

Sounds to me like it worked...  So what other problems does it have??
It does start like it should and wait AS it is suppose to for the
assigned 30 minutes...
Of course if ya had any Smarts at all, you would have changed the Sleep
settings to like 3 minutes
as I do when testing it out...

If it has Problems, where are they?  And I am NOT talking about coding
style.
What kind of helpful post states the Above AND not point out where it
is having problems...
but since you never fully tested it as far as I can tell from your
post,
how do you KNOW it is having problems or not?

Quite honestly...  None of Sinan's really helped at all...  Other then
to point out he doesn't like my coding style.
He failed to test it as far as I can tell.  He is running XP Pro, but
never came back with wether or not it
could connect and send a file to an FTP site...  Rather useless post in
many ways.



------------------------------

Date: 23 Feb 2005 12:59:52 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <cvhuo8$e9a$1@mamenchi.zrz.TU-Berlin.DE>

Dimitri Papoutsis  <bastard@uni-koblenz.de> wrote in comp.lang.perl.misc:
> A. Sinan Unur wrote:
> 
> Now some advice for you, son:
> If you want to help someone DO it... if not, then DO NOT mention the
> accordant thread. I had a look on your pseudo-trial to response "arek" in a

You can teach us how to run the newsgroup when you have some posting
history to speak of.  Until then your opinion is of little interest.

Oh, and look up "trial" in a dictionary.

Anno


------------------------------

Date: Wed, 23 Feb 2005 15:14:06 +0100
From: Dimitri Papoutsis <bastard@uni-koblenz.de>
Subject: Re: Annoying Problem with a Basic Perl app and XP Pro
Message-Id: <cvhva5$tna$1@news.uni-koblenz.de>

Anno Siegel wrote:

> Dimitri Papoutsis  <bastard@uni-koblenz.de> wrote in comp.lang.perl.misc:
>> A. Sinan Unur wrote:
>> 
>> Now some advice for you, son:
>> If you want to help someone DO it... if not, then DO NOT mention the
>> accordant thread. I had a look on your pseudo-trial to response "arek" in
>> a
> 
> You can teach us how to run the newsgroup when you have some posting
> history to speak of.  Until then your opinion is of little interest.

Oh , sorry daddy, i didn't know that... Will you please please forgive
me ...

> Oh, and look up "trial" in a dictionary.

all you said <=> q.e.d. (in my posting)

Danke Anno...  ;o)

        "trial <=> Versuch"     was exactly what i meant to say. i base my criticism 
                                upon your ignorance and missing ability of differentiated
                                thinking.

Kisses
Dimi


------------------------------

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc.  For subscription or unsubscription requests, send
#the single line:
#
#	subscribe perl-users
#or:
#	unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.  

NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice. 

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V10 Issue 7817
***************************************


home help back first fref pref prev next nref lref last post