------=_Part_7028_3315294.1193837808284
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,

I have the following code as part of my program;

 print "---=========> $file, $localFile\n";
                $sftp -> get( $file, $localFile ) || warn("errrrr0rrrrr
_---> $!".$sftp->status."\n");^M

Even though it has downloaded the file properly, it is giving the following
message:

---=========> /trading/tiscrdenhlist10310000.txt.old,
/export/home/crdadm/rajeev/tiscrdenhlist10310000.txt
errrrr0rrrrr _---> 0


Please let me know why it is give the error message.

Thanks,
Rajeev Kilaru

------=_Part_7028_3315294.1193837808284--

-----Original Message-----
>From: kilaru rajeev <kilarurajeev@gmail.com>

>                $sftp -> get( $file, $localFile ) || warn("errrrr0rrrrr
>_---> $!".$sftp->status."\n");^M
>
>Even though it has downloaded the file properly, it is giving the following
>message:
>
>---=========> /trading/tiscrdenhlist10310000.txt.old,
>/export/home/crdadm/rajeev/tiscrdenhlist10310000.txt
>errrrr0rrrrr _---> 0
>

You may check the document for Net::SFTP and see what's the return true for get() method.
If fetching a file with success and get() return 0, your `get() || warn()` statement will break.

T24gMTAvMzEvMDcsIGtpbGFydSByYWplZXYgPGtpbGFydXJhamVldkBnbWFpbC5jb20+IHdyb3Rl
Ogo+IEhpIEFsbCwKPgo+IEkgaGF2ZSB0aGUgZm9sbG93aW5nIGNvZGUgYXMgcGFydCBvZiBteSBw
cm9ncmFtOwo+Cj4gIHByaW50ICItLS09PT09PT09PT0+ICRmaWxlLCAkbG9jYWxGaWxlXG4iOwo+
ICAgICAgICAgICAgICAgICAkc2Z0cCAtPiBnZXQoICRmaWxlLCAkbG9jYWxGaWxlICkgfHwgd2Fy
bigiZXJycnJyMHJycnJyCj4gXy0tLT4gJCEiLiRzZnRwLT5zdGF0dXMuIlxuIik7Xk0KPgo+IEV2
ZW4gdGhvdWdoIGl0IGhhcyBkb3dubG9hZGVkIHRoZSBmaWxlIHByb3Blcmx5LCBpdCBpcyBnaXZp
bmcgdGhlIGZvbGxvd2luZwo+IG1lc3NhZ2U6Cj4KPiAtLS09PT09PT09PT0+IC90cmFkaW5nL3Rp
c2NyZGVuaGxpc3QxMDMxMDAwMC50eHQub2xkLAo+IC9leHBvcnQvaG9tZS9jcmRhZG0vcmFqZWV2
L3Rpc2NyZGVuaGxpc3QxMDMxMDAwMC50eHQKPiBlcnJycnIwcnJycnIgXy0tLT4gMAo+Cj4KPiBQ
bGVhc2UgbGV0IG1lIGtub3cgd2h5IGl0IGlzIGdpdmUgdGhlIGVycm9yIG1lc3NhZ2UuCj4KClJh
amVldiwKClRha2UgYW5vdGhlciBsb29rIGF0IHRoZSBOZXQ6OlNGVFAgZG9jcywgcGFydGljdWxh
cmx5IHRoZSBub3RlIGFib3V0CndoYXQgZ2V0KCkgZG9lcyB3aGVuIGNhbGxlZCBpbiBhIHZvaWQg
Y29udGV4dC4gVXNlICRzZnRwLT5zdGF0dXMsIG5vdAp0aGUgcmV0dXJuIHZhbHVlIG9mIGdldCgp
LCAgdG8gY2hlY2sgZm9yIGVycm9ycy4KCkJlc3QsCgotLSBqYXkKLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVGhpcyBlbWFpbCBhbmQgYXR0YWNobWVu
dChzKTogWyAgXSBibG9nYWJsZTsgWyB4IF0gYXNrIGZpcnN0OyBbICBdCnByaXZhdGUgYW5kIGNv
bmZpZGVudGlhbAoKZGFnZ2VycXVpbGwgW2F0XSBnbWFpbCBbZG90XSBjb20KaHR0cDovL3d3dy50
dWF3LmNvbSAgaHR0cDovL3d3dy5kb3dubG9hZHNxdWFkLmNvbSAgaHR0cDovL3d3dy5lbmdhdGlr
aS5vcmcKCnZhbHVlcyBvZiDiIHdpbGwgZ2l2ZSByaXNlIHRvIGRvbSEK

On 10/31/07, Jay Savage <daggerquill@gmail.com> wrote:

> Take another look at the Net::SFTP docs, particularly the note about
> what get() does when called in a void context.

I see a note about a non-void context, but I don't see one about a
void context. The OP didn't use the get() method in a void context.
Did you mean to write "non-void"?

    http://search.cpan.org/~dbrobins/Net-SFTP-0.10/lib/Net/SFTP.pm

As I interpret the docs, the OP's code should be correct. But maybe
I'm missing something.

--Tom Phoenix
Stonehenge Perl Training

On Oct 31, 11:15 am, t...@stonehenge.com (Tom Phoenix) wrote:
> On 10/31/07, Jay Savage <daggerqu...@gmail.com> wrote:
>
> > Take another look at the Net::SFTP docs, particularly the note about
> > what get() does when called in a void context.
>
> I see a note about a non-void context, but I don't see one about a
> void context. The OP didn't use the get() method in a void context.
> Did you mean to write "non-void"?
>
>    http://search.cpan.org/~dbrobins/Net-SFTP-0.10/lib/Net/SFTP.pm
>
> As I interpret the docs, the OP's code should be correct. But maybe
> I'm missing something.

It's correct unless the file the OP is retrieving happens to be empty
(or contains nothing but '0').

Paul Lalli

T24gMTAvMzEvMDcsIFRvbSBQaG9lbml4IDx0b21Ac3RvbmVoZW5nZS5jb20+IHdyb3RlOgo+IE9u
IDEwLzMxLzA3LCBKYXkgU2F2YWdlIDxkYWdnZXJxdWlsbEBnbWFpbC5jb20+IHdyb3RlOgo+Cj4g
PiBUYWtlIGFub3RoZXIgbG9vayBhdCB0aGUgTmV0OjpTRlRQIGRvY3MsIHBhcnRpY3VsYXJseSB0
aGUgbm90ZSBhYm91dAo+ID4gd2hhdCBnZXQoKSBkb2VzIHdoZW4gY2FsbGVkIGluIGEgdm9pZCBj
b250ZXh0Lgo+Cj4gSSBzZWUgYSBub3RlIGFib3V0IGEgbm9uLXZvaWQgY29udGV4dCwgYnV0IEkg
ZG9uJ3Qgc2VlIG9uZSBhYm91dCBhCj4gdm9pZCBjb250ZXh0LiBUaGUgT1AgZGlkbid0IHVzZSB0
aGUgZ2V0KCkgbWV0aG9kIGluIGEgdm9pZCBjb250ZXh0Lgo+IERpZCB5b3UgbWVhbiB0byB3cml0
ZSAibm9uLXZvaWQiPwo+Cj4gICAgIGh0dHA6Ly9zZWFyY2guY3Bhbi5vcmcvfmRicm9iaW5zL05l
dC1TRlRQLTAuMTAvbGliL05ldC9TRlRQLnBtCj4KPiBBcyBJIGludGVycHJldCB0aGUgZG9jcywg
dGhlIE9QJ3MgY29kZSBzaG91bGQgYmUgY29ycmVjdC4gQnV0IG1heWJlCj4gSSdtIG1pc3Npbmcg
c29tZXRoaW5nLgo+CgpJIHN1cHBvc2UgSSBzaG91bGQgaGF2ZSBzYWlkIG5vbi12b2lkLCBiZWNh
dXNlIHRoYXQgaXMgdGhlIGJlaGF2aW9yCnRoZSBkb2MgYWN0dWFsbHkgZGVzY3JpYmVzLgoKVGhl
IGFzc3VtcHRpb24sIHRob3VnaCwgaXMgdGhhdCB2b2lkIGNvbnRleHQgd2lsbCB5ZWlsZCB0aGUg
b3Bwb3NpdGUKcmVzdWx0LiBBbmQgaXQgbG9va3MgdG8gbWUgbGlrZSBPUCBpcyBjYWxsaW5nICRz
ZnRwLT5nZXQoKSBpbiBhIHZvaWQKY29udGV4dDoKCiAgICAkc2Z0cC0+Z2V0KCAkZmlsZSwgJGxv
Y2FsRmlsZSApIHx8IHdhcm4oImVycnJycjBycnJycl8tLS0+CiQhIi4kc2Z0cC0+c3RhdHVzLiJc
biIpOwoKQXQgbGVhc3QgSSdtIG5vdCBhd2FyZSB0aGF0IHRoYXQgJ3x8JyBmb3JjZXMgYW55IHBh
cnRpY3VsYXIgY29udGV4dCBvbgp0aGUgbGVmdGhhbmQgb3BlcmFuZC4gUGVybG9wIG1lbnRpb25z
IHByb3BhZ2F0aW5nIGNvbnRleHQgV1JUIHRoZQpyaWdodGhhbmQgb3BlcmFuZCwgYnV0IGRvZXNu
J3Qgc2F5IGFueXRoaW5nIGFib3V0IHRoZSBsZWZ0LiBTbyBJIHdvdWxkCmV4cGVjdCBnZXQoKSB0
byByZXR1cm4gdGhlIHNhbWUgaW4gdGhlIGZvbGxvd2luZyBjYXNlczoKCiAgICAkc2Z0cC0+Z2V0
KCAkZmlsZSwgJGxvY2FsRmlsZSk7CiAgICAkc2Z0cC0+Z2V0KCAkZmlsZSwgJGxvY2FsRmlsZSks
IHByaW50ICJzb21ldGhpbmciOwogICAgJHNmdHAtPmdldCggJGZpbGUsICRsb2NhbEZpbGUgKSB8
fCBkaWUoKTsKCkdpdmVuIHRoYXQsIEkgd291bGQgZXhwZWN0LCBmcm9tIHRoZSBkb2NzLCBmb3Ig
Z2V0KCkgdG8gcmV0dXJuIHRoZQplbXB0eSBzdHJpbmcgb24gc3VjY2VzcyBhbmQgdW5kZWYgb24g
ZmFpbHVyZSwgYm90aCBvZiB3aGljaCBhcmUKZXF1YWxseSBmYWxzZSBmcm9tIHRoZSBwZXJzcGVj
dGl2ZSBvZiAnfHwnLgoKT3IgbWF5YmUgKkknbSogbWlzc2luZyBzb21ldGhpbmc/CgotLWoKLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KVGhpcyBlbWFp
bCBhbmQgYXR0YWNobWVudChzKTogWyAgXSBibG9nYWJsZTsgWyB4IF0gYXNrIGZpcnN0OyBbICBd
CnByaXZhdGUgYW5kIGNvbmZpZGVudGlhbAoKZGFnZ2VycXVpbGwgW2F0XSBnbWFpbCBbZG90XSBj
b20KaHR0cDovL3d3dy50dWF3LmNvbSAgaHR0cDovL3d3dy5kb3dubG9hZHNxdWFkLmNvbSAgaHR0
cDovL3d3dy5lbmdhdGlraS5vcmcKCnZhbHVlcyBvZiDiIHdpbGwgZ2l2ZSByaXNlIHRvIGRvbSEK

Jay Savage wrote:
> On 10/31/07, Tom Phoenix <tom@stonehenge.com> wrote:
>> On 10/31/07, Jay Savage <daggerquill@gmail.com> wrote:
>>
>>> Take another look at the Net::SFTP docs, particularly the note about
>>> what get() does when called in a void context.
>> I see a note about a non-void context, but I don't see one about a
>> void context. The OP didn't use the get() method in a void context.
>> Did you mean to write "non-void"?
>>
>>     http://search.cpan.org/~dbrobins/Net-SFTP-0.10/lib/Net/SFTP.pm
>>
>> As I interpret the docs, the OP's code should be correct. But maybe
>> I'm missing something.
>>
> 
> I suppose I should have said non-void, because that is the behavior
> the doc actually describes.
> 
> The assumption, though, is that void context will yeild the opposite
> result. And it looks to me like OP is calling $sftp->get() in a void
> context:
> 
>     $sftp->get( $file, $localFile ) || warn("errrrr0rrrrr_--->
> $!".$sftp->status."\n");
> 
> At least I'm not aware that that '||' forces any particular context on
> the lefthand operand. Perlop mentions propagating context WRT the
> righthand operand, but doesn't say anything about the left. So I would
> expect get() to return the same in the following cases:
> 
>     $sftp->get( $file, $localFile);
>     $sftp->get( $file, $localFile), print "something";
>     $sftp->get( $file, $localFile ) || die();
> 
> Given that, I would expect, from the docs, for get() to return the
> empty string on success and undef on failure, both of which are
> equally false from the perspective of '||'.
> 
> Or maybe *I'm* missing something?

perl -e "@x=(1,2,3); print @x || 99;"

Rob

On 10/31/07, Jay Savage <daggerquill@gmail.com> wrote:

> it looks to me like OP is calling $sftp->get() in a void
> context:
>
>     $sftp->get( $file, $localFile ) || warn("errrrr0rrrrr_--->
> $!".$sftp->status."\n");

It may seem that way, but the left side of the logical or operator
isn't a void context, even if the operator itself is used in a void
context. That's actually a Boolean context (which is to say a scalar
context), no matter how the operator is used. That's because the left
side must be evaluated as true or false to determine whether the right
side will be evaluated, even if the whole thing is used in a void
context. Here comes the code:

  #!/usr/bin/perl

  use warnings;
  use strict;

  sub my_context {
    my $wa = wantarray ? "list" : "scalar";
    $wa = "void" unless defined wantarray;
    my $line = (caller)[2];
    print "Called in $wa context at line $line.\n";
    $wa;
  }

  print "Testing scalar and list context:\n";
  my $scalar = &my_context();
  my($list) = &my_context();
  print "Scalar: $scalar\nList: $list\n\n";

  print "Testing left side of ||-or in scalar context:\n";
  my $left_of_or = &my_context() || "0 but true";
  print "Left of ||-or: $left_of_or\n\n";

  print "Testing left side of ||-or in list context:\n";
  my($list_left_of_or) = &my_context() || "0 but true";
  print "List left of ||-or: $left_of_or\n\n";

  print "Testing left side of ||-or in void context:\n";
  &my_context() || die "no context";
  print "\n";

  print "Testing true void context:\n";
  &my_context();
  print "\n";

> At least I'm not aware that that '||' forces any particular context on
> the lefthand operand. Perlop mentions propagating context WRT the
> righthand operand, but doesn't say anything about the left.

The docs could always be more clear. The right operand of an
or-operator does inherit the context of the operator itself. But the
left operand's context is always Boolean.

> Given that, I would expect, from the docs, for get() to return the
> empty string on success

Where did you get that? From what I read of the docs, get() should
return the downloaded file contents on success. "If get is called in a
non-void context, returns the contents..."

  http://search.cpan.org/~dbrobins/Net-SFTP-0.10/lib/Net/SFTP.pm

Of course, the contents of a file could be the empty string or another
false value, so it would be appropriate to use defined() to test for
success.

Cheers!

--Tom Phoenix
Stonehenge Perl Training

This discussion let me think a thing that, one of my co-workers, who is good at both C and perl programming. When coding with Perl, he always like to put a 'return 0' on the end of each subroutines (maybe learn the habit from C?). So for his packages, the methods which were executed successfully will return 0. I think this behavior will make confuse for another perl caller. Is this not good prac  on Perl style?

-----Original Message-----
>From: Tom Phoenix <tom@stonehenge.com>
>Sent: Nov 1, 2007 2:21 AM
>To: Jay Savage <daggerquill@gmail.com>
>Cc: Perl List <beginners@perl.org>
>Subject: Re: Getting error in Net::SFTP with get function
>
>On 10/31/07, Jay Savage <daggerquill@gmail.com> wrote:
>
>> it looks to me like OP is calling $sftp->get() in a void
>> context:
>>
>>     $sftp->get( $file, $localFile ) || warn("errrrr0rrrrr_--->
>> $!".$sftp->status."\n");
>
>It may seem that way, but the left side of the logical or operator
>isn't a void context, even if the operator itself is used in a void
>context. That's actually a Boolean context (which is to say a scalar
>context), no matter how the operator is used. That's because the left
>side must be evaluated as true or false to determine whether the right
>side will be evaluated, even if the whole thing is used in a void
>context. Here comes the code:
>

T24gMTAvMzEvMDcsIFRvbSBQaG9lbml4IDx0b21Ac3RvbmVoZW5nZS5jb20+IHdyb3RlOgpbc25p
cF0KPiBUaGUgZG9jcyBjb3VsZCBhbHdheXMgYmUgbW9yZSBjbGVhci4gVGhlIHJpZ2h0IG9wZXJh
bmQgb2YgYW4KPiBvci1vcGVyYXRvciBkb2VzIGluaGVyaXQgdGhlIGNvbnRleHQgb2YgdGhlIG9w
ZXJhdG9yIGl0c2VsZi4gQnV0IHRoZQo+IGxlZnQgb3BlcmFuZCdzIGNvbnRleHQgaXMgYWx3YXlz
IEJvb2xlYW4uCj4KClRoYW5rcyBmb3IgY2xlYXJpbmcgdGhhdCB1cCEKCj4gPiBHaXZlbiB0aGF0
LCBJIHdvdWxkIGV4cGVjdCwgZnJvbSB0aGUgZG9jcywgZm9yIGdldCgpIHRvIHJldHVybiB0aGUK
PiA+IGVtcHR5IHN0cmluZyBvbiBzdWNjZXNzCj4KPiBXaGVyZSBkaWQgeW91IGdldCB0aGF0PyBG
cm9tIHdoYXQgSSByZWFkIG9mIHRoZSBkb2NzLCBnZXQoKSBzaG91bGQKPiByZXR1cm4gdGhlIGRv
d25sb2FkZWQgZmlsZSBjb250ZW50cyBvbiBzdWNjZXNzLiAiSWYgZ2V0IGlzIGNhbGxlZCBpbiBh
Cj4gbm9uLXZvaWQgY29udGV4dCwgcmV0dXJucyB0aGUgY29udGVudHMuLi4iCj4KClRoYXQncyBi
YWNrIHRvIHRoZSB3aG9sZSB2b2lkIGJ1c2luZXNzLiBJbiBhIHZvaWQgY29udGV4dCwgaXQgc2hv
dWxkCnJldHVybiB0aGUgZW1wdHkgc3RyaW5nIG9uIHN1Y2Nlc3MsIGFuZCB1bmRlZiBvbiBmYWls
dXJlLiBJbiBhbnkgb3RoZXIKY29udGV4dCwgaXQgc2hvdWxkIHJldHVybiB0aGUgZmlsZSBjb250
ZW50cyBvbiBzdWNjZXNzLiBDbGVhcmx5LCBJIHdhcwpjb25mdXNlZCBhYm91dCB0aGUgY29udGV4
dC4KClRoYW5rcyBmb3Igc29ydGluZyBtZSBvdXQuCgotLSBqCi0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClRoaXMgZW1haWwgYW5kIGF0dGFjaG1lbnQo
cyk6IFsgIF0gYmxvZ2FibGU7IFsgeCBdIGFzayBmaXJzdDsgWyAgXQpwcml2YXRlIGFuZCBjb25m
aWRlbnRpYWwKCmRhZ2dlcnF1aWxsIFthdF0gZ21haWwgW2RvdF0gY29tCmh0dHA6Ly93d3cudHVh
dy5jb20gIGh0dHA6Ly93d3cuZG93bmxvYWRzcXVhZC5jb20gIGh0dHA6Ly93d3cuZW5nYXRpa2ku
b3JnCgp2YWx1ZXMgb2Yg4iB3aWxsIGdpdmUgcmlzZSB0byBkb20hCg==

From:           	Jeff Pang <pangj@earthlink.net>
> This discussion let me think a thing that, one of my co-workers, who
> is good at both C and perl programming. When coding with Perl, he
> always like to put a 'return 0' on the end of each subroutines (maybe
> learn the habit from C?). So for his packages, the methods which were
> executed successfully will return 0. I think this behavior will make
> confuse for another perl caller. Is this not good prac  on Perl style? 

It would definitely confuse me. And drive me up the wall. 
I would kinda expect this from a module that's just a thin wrapper 
around a C library, but from an OO module that was written in Perl? 
Nope.

Jenda
===== Jenda@Krynicky.cz === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed 
to get drunk and croon as much as they like.
	-- Terry Pratchett in Sourcery

On Nov 1, 9:10 am, daggerqu...@gmail.com (Jay Savage) wrote:
> That's back to the whole void business. In a void context, it should
> return the empty string on success, and undef on failure. In any other
> context, it should return the file contents on success. Clearly, I was
> confused about the context.

You are still confused about context.  It makes no sense to return
ANYTHING in void context.  Void context very specifically means that
the return value is not used, looked at, or stored in any way.

Paul Lalli