[33015] in Perl-Users-Digest
Perl-Users Digest, Issue: 4291 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Oct 1 09:09:19 2014
Date: Wed, 1 Oct 2014 06:09:05 -0700 (PDT)
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, 1 Oct 2014 Volume: 11 Number: 4291
Today's topics:
clever equal still experimental after so much time <gravitalsun@hotmail.foo>
Re: clever equal still experimental after so much time <gamo@telecable.es>
Re: clever equal still experimental after so much time <rweikusat@mobileactivedefense.com>
Re: clever equal still experimental after so much time <gamo@telecable.es>
Re: clever equal still experimental after so much time <rweikusat@mobileactivedefense.com>
Re: clever equal still experimental after so much time <gamo@telecable.es>
Re: clever equal still experimental after so much time (Tim McDaniel)
Re: clever equal still experimental after so much time <justin.1401@purestblue.com>
Re: clever equal still experimental after so much time <rweikusat@mobileactivedefense.com>
creating scalar references via eval <rweikusat@mobileactivedefense.com>
Re: creating scalar references via eval <gravitalsun@hotmail.foo>
Re: creating scalar references via eval <rweikusat@mobileactivedefense.com>
do vs sub <gravitalsun@hotmail.foo>
Re: do vs sub <m@rtij.nl.invlalid>
Re: do vs sub <rweikusat@mobileactivedefense.com>
Re: do vs sub <peter@makholm.net>
Re: do vs sub <rweikusat@mobileactivedefense.com>
Re: Open fail on ouput file - SOLVED <No-Spam@deezee.org>
Re: Open fail on ouput file - SOLVED <gravitalsun@hotmail.foo>
Re: Open fail on ouput file <gravitalsun@hotmail.foo>
Re: Open fail on ouput file <No-Spam@deezee.org>
Re: Open fail on ouput file <gravitalsun@hotmail.foo>
Re: Open fail on ouput file <lionslair@consolidated.net>
Re: Open fail on ouput file <No-Spam@deezee.org>
Perldancer isolation <gravitalsun@hotmail.foo>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 29 Sep 2014 13:32:53 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: clever equal still experimental after so much time
Message-Id: <m0bcfm$nf1$1@news.ntua.gr>
use strict;
use warnings;
my %hash = qw/k1 1 k2 0 k3 1/;
print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
------------------------------
Date: Mon, 29 Sep 2014 13:42:21 +0200
From: gamo <gamo@telecable.es>
Subject: Re: clever equal still experimental after so much time
Message-Id: <m0bgir$87l$1@speranza.aioe.org>
El 29/09/14 a las 12:32, George Mpouras escribió:
> use strict;
> use warnings;
> my %hash = qw/k1 1 k2 0 k3 1/;
>
> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
nope
As expected, because $_[0] is undef
--
http://www.telecable.es/personales/gamo/
------------------------------
Date: Mon, 29 Sep 2014 13:06:18 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: clever equal still experimental after so much time
Message-Id: <87oatyy6kl.fsf@doppelsaurus.mobileactivedefense.com>
gamo <gamo@telecable.es> writes:
> El 29/09/14 a las 12:32, George Mpouras escribió:
>> use strict;
>> use warnings;
>> my %hash = qw/k1 1 k2 0 k3 1/;
>>
>> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
>
> nope
>
> As expected, because $_[0] is undef
-----------
use strict;
use warnings;
my %hash = qw/k1 1 k2 1 k3 1/;
print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
-----------
will print 'all true' because the 0 associated with k2 has been
changed to a 1.
------------------------------
Date: Mon, 29 Sep 2014 20:44:37 +0200
From: gamo <gamo@telecable.es>
Subject: Re: clever equal still experimental after so much time
Message-Id: <m0c9ai$a2a$1@speranza.aioe.org>
El 29/09/14 a las 14:06, Rainer Weikusat escribió:
> gamo <gamo@telecable.es> writes:
>> El 29/09/14 a las 12:32, George Mpouras escribió:
>>> use strict;
>>> use warnings;
>>> my %hash = qw/k1 1 k2 0 k3 1/;
>>>
>>> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
>>
>> nope
>>
>> As expected, because $_[0] is undef
>
> -----------
> use strict;
> use warnings;
> my %hash = qw/k1 1 k2 1 k3 1/;
>
> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
> -----------
>
> will print 'all true' because the 0 associated with k2 has been
> changed to a 1.
>
Ok, so is not a problem related with $_[0], which is feeded,
but with $hash{k2} which returns 0 and 0 is take as false.
If this is expected or unexpected depends only on the specifications.
It's not obvious to me what is the desired behavior.
--
http://www.telecable.es/personales/gamo/
------------------------------
Date: Mon, 29 Sep 2014 19:56:26 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: clever equal still experimental after so much time
Message-Id: <87eguuw90l.fsf@doppelsaurus.mobileactivedefense.com>
gamo <gamo@telecable.es> writes:
> El 29/09/14 a las 14:06, Rainer Weikusat escribió:
>> gamo <gamo@telecable.es> writes:
>>> El 29/09/14 a las 12:32, George Mpouras escribió:
>>>> use strict;
>>>> use warnings;
>>>> my %hash = qw/k1 1 k2 0 k3 1/;
>>>>
>>>> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
>>>
>>> nope
>>>
>>> As expected, because $_[0] is undef
>>
>> -----------
>> use strict;
>> use warnings;
>> my %hash = qw/k1 1 k2 1 k3 1/;
>>
>> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
>> -----------
>>
>> will print 'all true' because the 0 associated with k2 has been
>> changed to a 1.
>>
>
> Ok, so is not a problem related with $_[0], which is feeded,
> but with $hash{k2} which returns 0 and 0 is take as false.
>
> If this is expected or unexpected depends only on the specifications.
> It's not obvious to me what is the desired behavior.
%hash ~~ sub { $hash{$_[0]} }
is a so-called 'smart match' and its roughly equivalent to
sub all_true
{
$hash{$_} or return for keys(%hash);
return 1;
}
ie, the subroutine to the right is called for all keys of the hash and
the operator will return true if the subroutine always returned true.
The problem with this (and 'smart matching' in general) is that
there's no obvious reason why trying to 'match' a hash against a code
reference should mean this (or mean anything at all, FWIW), cf
http://www.catb.org/jargon/html/D/DWIM.html
------------------------------
Date: Mon, 29 Sep 2014 21:18:14 +0200
From: gamo <gamo@telecable.es>
Subject: Re: clever equal still experimental after so much time
Message-Id: <m0cb9j$fgu$1@speranza.aioe.org>
El 29/09/14 a las 20:56, Rainer Weikusat escribió:
>> Ok, so is not a problem related with $_[0], which is feeded,
>> but with $hash{k2} which returns 0 and 0 is take as false.
>>
>> If this is expected or unexpected depends only on the specifications.
>> It's not obvious to me what is the desired behavior.
>
> %hash ~~ sub { $hash{$_[0]} }
>
> is a so-called 'smart match' and its roughly equivalent to
>
> sub all_true
> {
> $hash{$_} or return for keys(%hash);
> return 1;
> }
>
> ie, the subroutine to the right is called for all keys of the hash and
> the operator will return true if the subroutine always returned true.
>
> The problem with this (and 'smart matching' in general) is that
> there's no obvious reason why trying to 'match' a hash against a code
> reference should mean this (or mean anything at all, FWIW), cf
>
> http://www.catb.org/jargon/html/D/DWIM.html
>
Thanks for the link, very interesting
http://jargon.net/jargonfile/h/hairy.html
--
http://www.telecable.es/personales/gamo/
------------------------------
Date: Tue, 30 Sep 2014 21:04:48 +0000 (UTC)
From: tmcd@panix.com (Tim McDaniel)
Subject: Re: clever equal still experimental after so much time
Message-Id: <m0f5tg$deg$1@reader1.panix.com>
In article <m0c9ai$a2a$1@speranza.aioe.org>, gamo <gamo@telecable.es> wrote:
>It's not obvious to me what is the desired behavior.
I believe that's the common complaint about many cases of ~~.
--
Tim McDaniel, tmcd@panix.com
------------------------------
Date: Wed, 1 Oct 2014 08:45:29 +0100
From: Justin C <justin.1401@purestblue.com>
Subject: Re: clever equal still experimental after so much time
Message-Id: <p1osfb-gqh.ln1@zem.masonsmusic.co.uk>
On 2014-09-29, George Mpouras <gravitalsun@hotmail.foo> wrote:
> use strict;
> use warnings;
> my %hash = qw/k1 1 k2 0 k3 1/;
>
> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
Smartmatch is experimental.
"If something in the Perl core is marked as experimental, we may
change its behaviour, deprecate or remove it without notice. While
we'll always do our best to smooth the transition path for users of
experimental features, you should contact the perl5-porters
mailinglist if you find an experimental feature useful and want to
help shape its future."
In other words, don't use it because it might do something
different next week. If you can cope with that, go ahead but
you'd be a fool to put it in production code just yet.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Wed, 01 Oct 2014 13:17:55 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: clever equal still experimental after so much time
Message-Id: <878ul0f0gc.fsf@doppelsaurus.mobileactivedefense.com>
Justin C <justin.1401@purestblue.com> writes:
> On 2014-09-29, George Mpouras <gravitalsun@hotmail.foo> wrote:
>> use strict;
>> use warnings;
>> my %hash = qw/k1 1 k2 0 k3 1/;
>>
>> print %hash ~~ sub{$hash{$_[0]}} ? 'all true' : 'nope'
>
> Smartmatch is experimental.
>
> "If something in the Perl core is marked as experimental, we may
> change its behaviour, deprecate or remove it without notice. While
> we'll always do our best to smooth the transition path for users of
> experimental features, you should contact the perl5-porters
> mailinglist if you find an experimental feature useful and want to
> help shape its future."
That's an invitation for users of experimental features to consider
participiating in their future development.
> In other words, don't use it because it might do something
> different next week. If you can cope with that, go ahead but
> you'd be a fool to put it in production code just yet.
And that's a non-sequitur: Some future (or already released but
'relatively future') Perl version may "change the behaviour of the
feature or remove it". Consequently, such a Perl version possibly can't
be used for known-be-working production code, at least not without
either changing the former or the latter.
------------------------------
Date: Mon, 29 Sep 2014 15:09:41 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: creating scalar references via eval
Message-Id: <87d2aey0uy.fsf@doppelsaurus.mobileactivedefense.com>
Data::Dumper uses code similar to this
bless(do{\(my $o = "lonweb.mwam.remote")},'MES::Hostname')
when serializing scalar references. It is possible to achieve something
apparently equivalent by calling a suitable, locally-bound function, eg
do{
local *scalarr_ = sub { \$_[0] };
[
bless(scalarr_("team7jailbreak.com"), 'MES::Hostname'),
bless(scalarr_("www.7jailbreak.com"), 'MES::Hostname'),
bless(scalarr_("m.whatismyip.com"), 'MES::Hostname'),
bless(scalarr_("www.whatismyip.com"), 'MES::Hostname')
]
};
which has less textual overhead per reference and (IMHO) looks somewhat
less like "dark magic" to the casual observer. A side effect would be
that all scalar references created in this way end up as PVMGs. This
doesn't really concern me because I'm creating objects, anyway, and also
doesn't seem to be something to worry about if this wasn't the case.
Are there other, less pleasant, side effects?
------------------------------
Date: Mon, 29 Sep 2014 19:50:28 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: Re: creating scalar references via eval
Message-Id: <m0c2kn$29hs$1@news.ntua.gr>
There is absolute no problem at your code , but I am wondering how
usefull can be blessing multiple refs at the same package.
I mean whatever the internal crazyness the "new" conrstruct methods
usually return one ! Thats how the human brain works.
Ok you could return many , but who is going to use it , Mr.Spok maybe !
------------------------------
Date: Mon, 29 Sep 2014 18:46:33 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: creating scalar references via eval
Message-Id: <87iok6wc92.fsf@doppelsaurus.mobileactivedefense.com>
George Mpouras <gravitalsun@hotmail.foo> writes:
> There is absolute no problem at your code , but I am wondering how
> usefull can be blessing multiple refs at the same package.
> I mean whatever the internal crazyness the "new" conrstruct methods
> usually return one ! Thats how the human brain works.
When evaluated, the do { } returns a references to an anonymous array
containing references to scalars blessed into a class MES::Hostnames,
ie, an array of 'hostname' objects. The example was a 'real-world'
serialization file of the 'hostname database' of some program.
------------------------------
Date: Mon, 29 Sep 2014 22:16:54 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: do vs sub
Message-Id: <m0cb7a$2scq$1@news.ntua.gr>
to my suprise the "return" from within a do block have behaves the same
as returning from a subroutine so the following two are equivelant
return if sub{ foreach (keys %conditions_are_satisfied) {return 0
unless $conditions_are_satisfied{$_}} 1}->()
return if do{ foreach (keys %conditions_are_satisfied) {return 0 unless
$conditions_are_satisfied{$_}} 1}
cool !
------------------------------
Date: Tue, 30 Sep 2014 08:54:41 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: do vs sub
Message-Id: <hm0qfb-ruu.ln1@news.rtij.nl>
On Mon, 29 Sep 2014 22:16:54 +0300, George Mpouras wrote:
> to my suprise the "return" from within a do block have behaves the same
> as returning from a subroutine so the following two are equivelant
>
>
> return if sub{ foreach (keys %conditions_are_satisfied) {return 0
> unless $conditions_are_satisfied{$_}} 1}->()
>
> return if do{ foreach (keys %conditions_are_satisfied) {return 0 unless
> $conditions_are_satisfied{$_}} 1}
Can't return outside a subroutine at -e line 1.
M4
------------------------------
Date: Tue, 30 Sep 2014 12:23:00 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: do vs sub
Message-Id: <87fvf9gxnv.fsf@doppelsaurus.mobileactivedefense.com>
George Mpouras <gravitalsun@hotmail.foo> writes:
[...]
> return if sub{ foreach (keys %conditions_are_satisfied) {return 0
> unless $conditions_are_satisfied{$_}} 1}->()
A more general remark: I'm very sorely tempted to refer to this as 'a
coding GAU' ('Groesster Anzunehmender Unfug', something like 'most
stupid conceivable idea', parallelling 'Groesster Anzunehmender Unfall',
'greatest possible disaster', referring to explosion of a nuclear
reactor) as this creates a single-call subroutine and calls it, thereby
suffering from whatever 'function call overhead' exists in exchange for
making the code more complicated.
Putting this into a named subroutine,
sub all_true
{
$_ or return for values(%{$_[0]});
return 1;
}
and using this like
return if all_true(\%conditions);
or
return unless all_true(\%conditions);
will make the code much easier to deal with (and understand) at the
point of the call and details about the exact implementation of the
test don't matter there.
------------------------------
Date: Tue, 30 Sep 2014 13:29:57 +0200
From: Peter Makholm <peter@makholm.net>
Subject: Re: do vs sub
Message-Id: <871tqtxs5m.fsf@vps1.hacking.dk>
George Mpouras <gravitalsun@hotmail.foo> writes:
> to my suprise the "return" from within a do block have behaves the
> same as returning from a subroutine so the following two are
> equivelant
>
>
> return if sub{ foreach (keys %conditions_are_satisfied) {return 0
> unless $conditions_are_satisfied{$_}} 1}->()
I would expect this to unconditionally return an empty list (or undef in
scalar context) as a anonymous sub reference is always true.
> return if do{ foreach (keys %conditions_are_satisfied) {return 0
> unless $conditions_are_satisfied{$_}} 1}
If $conditions_are_satisfied{$_} are true for one of the keys I would
expect this to return the value 0, otherwise I would expect it not to
return and proceed to the following line. If this is the last line in
the subroutine I expect it to return some the last false value it sees
from $conditions_are_satisfied.
//Makholm
------------------------------
Date: Tue, 30 Sep 2014 13:22:45 +0100
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: do vs sub
Message-Id: <87tx3pfgbu.fsf@doppelsaurus.mobileactivedefense.com>
Peter Makholm <peter@makholm.net> writes:
> George Mpouras <gravitalsun@hotmail.foo> writes:
>
>> to my suprise the "return" from within a do block have behaves the
>> same as returning from a subroutine so the following two are
>> equivelant
>>
>>
>> return if sub{ foreach (keys %conditions_are_satisfied) {return 0
>> unless $conditions_are_satisfied{$_}} 1}->()
>
> I would expect this to unconditionally return an empty list (or undef in
> scalar context) as a anonymous sub reference is always true.
I'd like to submit this as 'exhibit A' re: making the code more
complicated. The subroutine is actually called on-the-spot, see trailing
->().
------------------------------
Date: Sun, 28 Sep 2014 12:58:21 +0000 (UTC)
From: "Dave Saville" <No-Spam@deezee.org>
Subject: Re: Open fail on ouput file - SOLVED
Message-Id: <fV45K0OBJxbE-pn2-dyjPukp3ZXg9@paddington.bear.den>
On Sun, 28 Sep 2014 08:58:55 UTC, "Dave Saville" <No-Spam@deezee.org>
wrote:
Duh - The path had got screwed and it could not find sh - Shame that
"No such file or directory " does not say *what* it can't find. Would
have sussed this straight away :-(
Sorry to bother you.
--
Regards
Dave Saville
------------------------------
Date: Sun, 28 Sep 2014 22:24:59 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: Re: Open fail on ouput file - SOLVED
Message-Id: <m09nad$280j$1@news.ntua.gr>
On 28/9/2014 3:58 μμ, Dave Saville wrote:
> On Sun, 28 Sep 2014 08:58:55 UTC, "Dave Saville" <No-Spam@deezee.org>
> wrote:
>
> Duh - The path had got screwed and it could not find sh - Shame that
> "No such file or directory " does not say *what* it can't find. Would
> have sussed this straight away :-(
>
> Sorry to bother you.
>
no problem bro.
------------------------------
Date: Sat, 27 Sep 2014 17:34:43 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: Re: Open fail on ouput file
Message-Id: <m06hv3$9mj$1@news.ntua.gr>
On 27/9/2014 2:06 μμ, Dave Saville wrote:
> or die "Can't fork $!";
make the
or die "Can't fork $!";
or die "Oups \"$?\" no... \"$^E\"\n";
and come back with the error message
------------------------------
Date: Sat, 27 Sep 2014 20:08:59 +0000 (UTC)
From: "Dave Saville" <No-Spam@deezee.org>
Subject: Re: Open fail on ouput file
Message-Id: <fV45K0OBJxbE-pn2-5ZtCIdcBWVDd@paddington.bear.den>
On Sat, 27 Sep 2014 14:34:43 UTC, George Mpouras
<gravitalsun@hotmail.foo> wrote:
> On 27/9/2014 2:06 , Dave Saville wrote:
> > or die "Can't fork $!";
>
> make the
> or die "Can't fork $!";
> or die "Oups \"$?\" no... \"$^E\"\n";
>
> and come back with the error message
backup_incremental.pl
Starting incremental backup @ 2014_09_27_21_08_15
Cleaning C:
Searching for old incrementals of C
Incremental backup for C:
zip -@ -n
".z;.gz;.zip;.zoo;.arc;.lzh;.arj;.jar;.jpg;.jpeg;.mov;.avi;.gif;.epub"
-8 -S T:/Backup/PADDINGTON/2014_09_27_21_08_15_C.zip
Oups "0" no... ""
--
Regards
Dave Saville
------------------------------
Date: Sun, 28 Sep 2014 00:57:30 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: Re: Open fail on ouput file
Message-Id: <m07bs9$24gq$1@news.ntua.gr>
On 27/9/2014 11:08 μμ, Dave Saville wrote:
> On Sat, 27 Sep 2014 14:34:43 UTC, George Mpouras
> <gravitalsun@hotmail.foo> wrote:
>
>> On 27/9/2014 2:06 , Dave Saville wrote:
>>> or die "Can't fork $!";
>>
>> make the
>> or die "Can't fork $!";
>> or die "Oups \"$?\" no... \"$^E\"\n";
>>
>> and come back with the error message
>
> backup_incremental.pl
> Starting incremental backup @ 2014_09_27_21_08_15
> Cleaning C:
> Searching for old incrementals of C
> Incremental backup for C:
> zip -@ -n
> ".z;.gz;.zip;.zoo;.arc;.lzh;.arj;.jar;.jpg;.jpeg;.mov;.avi;.gif;.epub"
> -8 -S T:/Backup/PADDINGTON/2014_09_27_21_08_15_C.zip
> Oups "0" no... ""
>
zip util tries to update the
T:/Backup/PADDINGTON/2014_09_27_11_43_17_C.zip
and for reason it can not read it. Try to issue the same command as
script, from a "dos" console manual to see what happens.
is the zip file there ?
------------------------------
Date: Sat, 27 Sep 2014 20:57:56 -0500
From: Martin Eastburn <lionslair@consolidated.net>
Subject: Re: Open fail on ouput file
Message-Id: <0XJVv.267419$JH1.230746@fx08.iad>
On 9/27/2014 4:57 PM, George Mpouras wrote:
> On 27/9/2014 11:08 μμ, Dave Saville wrote:
>> On Sat, 27 Sep 2014 14:34:43 UTC, George Mpouras
>> <gravitalsun@hotmail.foo> wrote:
>>
>>> On 27/9/2014 2:06 , Dave Saville wrote:
>>>> or die "Can't fork $!";
>>>
>>> make the
>>> or die "Can't fork $!";
>>> or die "Oups \"$?\" no... \"$^E\"\n";
>>>
>>> and come back with the error message
>>
>> backup_incremental.pl
>> Starting incremental backup @ 2014_09_27_21_08_15
>> Cleaning C:
>> Searching for old incrementals of C
>> Incremental backup for C:
>> zip -@ -n
>> ".z;.gz;.zip;.zoo;.arc;.lzh;.arj;.jar;.jpg;.jpeg;.mov;.avi;.gif;.epub"
>> -8 -S T:/Backup/PADDINGTON/2014_09_27_21_08_15_C.zip
>> Oups "0" no... ""
>>
>
>
>
> zip util tries to update the
> T:/Backup/PADDINGTON/2014_09_27_11_43_17_C.zip
> and for reason it can not read it. Try to issue the same command as
> script, from a "dos" console manual to see what happens.
> is the zip file there ?
Is the logical disk T mounted ? or was it remapped to another letter.
Does it die on the Disk, or disk space or folders already made?
Martin
------------------------------
Date: Sun, 28 Sep 2014 08:58:55 +0000 (UTC)
From: "Dave Saville" <No-Spam@deezee.org>
Subject: Re: Open fail on ouput file
Message-Id: <fV45K0OBJxbE-pn2-GNe80fdzxCcp@paddington.bear.den>
On Sun, 28 Sep 2014 01:57:56 UTC, Martin Eastburn
<lionslair@consolidated.net> wrote:
> On 9/27/2014 4:57 PM, George Mpouras wrote:
> > On 27/9/2014 11:08 , Dave Saville wrote:
> >> On Sat, 27 Sep 2014 14:34:43 UTC, George Mpouras
> >> <gravitalsun@hotmail.foo> wrote:
> >>
> >>> On 27/9/2014 2:06 , Dave Saville wrote:
> >>>> or die "Can't fork $!";
> >>>
> >>> make the
> >>> or die "Can't fork $!";
> >>> or die "Oups \"$?\" no... \"$^E\"\n";
> >>>
> >>> and come back with the error message
> >>
> >> backup_incremental.pl
> >> Starting incremental backup @ 2014_09_27_21_08_15
> >> Cleaning C:
> >> Searching for old incrementals of C
> >> Incremental backup for C:
> >> zip -@ -n
> >> ".z;.gz;.zip;.zoo;.arc;.lzh;.arj;.jar;.jpg;.jpeg;.mov;.avi;.gif;.epub"
> >> -8 -S T:/Backup/PADDINGTON/2014_09_27_21_08_15_C.zip
> >> Oups "0" no... ""
> >>
> >
> >
> >
> > zip util tries to update the
> > T:/Backup/PADDINGTON/2014_09_27_11_43_17_C.zip
> > and for reason it can not read it. Try to issue the same command as
> > script, from a "dos" console manual to see what happens.
> > is the zip file there ?
> Is the logical disk T mounted ? or was it remapped to another letter.
> Does it die on the Disk, or disk space or folders already made?
Yes it's mounted. Why has zip suddenly decided to try and read a file
it is supposed to be creating?
[D:\bin]zip -@ -n
".z;.gz;.zip;.zoo;.arc;.lzh;.arj;.jar;.jpg;.jpeg;.mov;.avi;.gi
f;.epub" -8 -S T:/Backup/PADDINGTON/2014_09_28_09_54_13_C.zip
c:/config.sys
^Z
adding: config.sys (deflated 61%)
ls -lrt t:/backup/paddington
-rw-r--r-- 1 root 0 4011 Sep 28 09:55 2014_09_28_09_54_13_C.zip
It's working on an identical box and work on this one until two days
ago. Nothing has been updated recently.
--
Regards
Dave Saville
------------------------------
Date: Tue, 30 Sep 2014 15:59:21 +0300
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: Perldancer isolation
Message-Id: <m0e9ea$1sai$1@news.ntua.gr>
I create anweb app using the Dancer module, which works fine. If I use
the web app from an other PC, I can see the forms filled with params I
used at the first PC. So I am freaked out. Everything is stateless; no
cookies or stored data at db/files.
Do you know anything about ?
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 V11 Issue 4291
***************************************
