[29663] in Perl-Users-Digest
Perl-Users Digest, Issue: 907 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 5 06:09:44 2007
Date: Fri, 5 Oct 2007 03:09:04 -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 Fri, 5 Oct 2007 Volume: 11 Number: 907
Today's topics:
Re: @_ zero byte problem <hjp-usenet2@hjp.at>
Re: @_ zero byte problem <paduille.4061.mumia.w+nospam@earthlink.net>
Re: how do you fix newnews? <tadmc@seesig.invalid>
Re: how do you fix newnews? <kkeller-usenet@wombat.san-francisco.ca.us>
Re: How to manipulate the cases of letters in a string? <stoupa@practisoft.cz>
Re: How to manipulate the cases of letters in a string? <sbryce@scottbryce.com>
Re: How to manipulate the cases of letters in a string? <rprp@gmx.net>
Re: optimal vs. optimized [was: Re: string concatentati <vocabulary49@gmail.com>
Re: perl join on a non printable variable character ? <dummy@example.com>
Re: perl join on a non printable variable character ? <tony@skelding.co.uk>
Re: perl join on a non printable variable character ? <rkb@i.frys.com>
Re: perl join on a non printable variable character ? <stoupa@practisoft.cz>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: SIG{'PIPE'} <stoupa@practisoft.cz>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 5 Oct 2007 09:29:02 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: @_ zero byte problem
Message-Id: <slrnfgbpu4.ak5.hjp-usenet2@zeno.hjp.at>
On 2007-10-04 01:36, Mumia W. <paduille.4061.mumia.w+nospam@earthlink.net> wrote:
> On 10/03/2007 08:03 PM, Jeff wrote:
>> I have a sub where I pass in a "binary" and write it to a file
>> something like:
>>
>> sub storeImage{
>> my ($image) = @_;
>>
>>
>> open(IF,">$ENV{DOCUMENT_ROOT}/test.jpg") or die "$!";
>> binmode IF;
>> while (read($image,$Buffer,1024)){print IF $Buffer;}
>> close (IF)|| die "$!";
>> }
>>
>> Now, when I run that it prints a 0 byte file, it didn't used to.
Check for errors.
> I don't know what's wrong with the server, but try this:
>
> my $image = $_[0];
How should this be different from my ($image) = @_;? (But I don't
understand why shift should make a difference, either)
From the use of $ENV{DOCUMENT_ROOT} I guess that this is a script using
the CGI module, and that the parameter of storeImage is the result from
param('file_upload_parameter'), which is magic and sometimes behaves
strangely. perldoc CGI says:
However, there are problems with the dual nature of the upload fields.
[...]
To be safe, use the upload() function (new in version 2.47). When
called with the name of an upload field, upload() returns a filehandle,
or undef if the parameter is not a valid filehandle.
> Even better, use File::Slurp;
>
> use File::Slurp;
>
> sub storeImage {
> my $image = shift;
> write_file("$ENV{DOCUMENT_ROOT}/test.jpg", $image);
> }
That's not the same. In the OP's code, $image is (or should be) a file
handle, from which data is copied. write_file expects a string here.
> Is that not simpler? :-)
For every problem there is a solution which is simple, neat, and wrong.
:-)
hp
--
_ | Peter J. Holzer | I know I'd be respectful of a pirate
|_|_) | Sysadmin WSR | with an emu on his shoulder.
| | | hjp@hjp.at |
__/ | http://www.hjp.at/ | -- Sam in "Freefall"
------------------------------
Date: Fri, 05 Oct 2007 03:49:57 -0500
From: "Mumia W." <paduille.4061.mumia.w+nospam@earthlink.net>
Subject: Re: @_ zero byte problem
Message-Id: <13gbuubb49qd949@corp.supernews.com>
On 10/05/2007 02:29 AM, Peter J. Holzer wrote:
>
> That's not the same. In the OP's code, $image is (or should be) a file
> handle, from which data is copied. write_file expects a string here.
>
Oh yes. I completely overlooked Jeff's while statement wherein he used
read(). I read his text, and he said he was passing in a "binary."
------------------------------
Date: Fri, 05 Oct 2007 01:32:52 GMT
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: how do you fix newnews?
Message-Id: <slrnfgb4vk.8ug.tadmc@tadmc30.sbcglobal.net>
Wade Ward <zaxfuuq@invalid.net> wrote:
> Subject: how do you fix newnews?
Take it to a veterinarian.
Oh. I thought you said "mewmews"...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Thu, 4 Oct 2007 20:40:59 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: how do you fix newnews?
Message-Id: <cbogt4xhch.ln2@goaway.wombat.san-francisco.ca.us>
On 2007-10-05, Wade Ward <zaxfuuq@invalid.net> wrote:
>
> I won't re-read the posting guidleienes.
Good luck getting help from clpmisc in the future.
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: Fri, 5 Oct 2007 06:29:56 +0200
From: "Petr Vileta" <stoupa@practisoft.cz>
Subject: Re: How to manipulate the cases of letters in a string?
Message-Id: <fe4fgi$1623$1@ns.felk.cvut.cz>
Jim Gibson wrote:
> In article <1191541667.632448.15320@g4g2000hsf.googlegroups.com>, xz
> <zhang.xi.cn@gmail.com> wrote:
>
>> Say, change "i LOVE this Game" into "I LOVE THIS GAME" or "i love
>> this game"
>
> perldoc -f uc
> perldoc -f lc
Your answer is short and to the subject, but not all perl programmers use
Linux. I can mention only that some of us are using ActiveState Perl and we
have not any perldoc.exe on our Windows PCs :-)
Maybe will be better to write some "OS independent", e.g. "look at function
uc()".
I don't know what type of documentation is on Mac.
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail. Send me your mail
from another non-spammer site please.)
------------------------------
Date: Thu, 04 Oct 2007 23:16:36 -0600
From: Scott Bryce <sbryce@scottbryce.com>
Subject: Re: How to manipulate the cases of letters in a string?
Message-Id: <kOadnVCjV-8lVZjanZ2dnUVZ_v-hnZ2d@comcast.com>
Petr Vileta wrote:
> Your answer is short and to the subject, but not all perl programmers
> use Linux. I can mention only that some of us are using ActiveState Perl
> and we have not any perldoc.exe on our Windows PCs :-)
Yes, we do. I'm on Windows Vista, and it works for me. Even if it
didn't, so what? I can always go to perldoc.perl.org and do a search for
uc and lc.
The answer Jim Gibson gave is fine, even for those of us on Windows.
------------------------------
Date: Fri, 05 Oct 2007 10:15:58 +0200
From: Reinhard Pagitsch <rprp@gmx.net>
Subject: Re: How to manipulate the cases of letters in a string?
Message-Id: <4705f2bf$0$90272$14726298@news.sunsite.dk>
Petr Vileta wrote:
> Jim Gibson wrote:
>> In article <1191541667.632448.15320@g4g2000hsf.googlegroups.com>, xz
>> <zhang.xi.cn@gmail.com> wrote:
>>
>>> Say, change "i LOVE this Game" into "I LOVE THIS GAME" or "i love
>>> this game"
>>
>> perldoc -f uc
>> perldoc -f lc
>
> Your answer is short and to the subject, but not all perl programmers
> use Linux. I can mention only that some of us are using ActiveState Perl
> and we have not any perldoc.exe on our Windows PCs :-)
We have perldoc.bat on our system in the \perl\bin directory.
And we have also the HTML documentation under \perl\html.
Simply open the index.html, in the left frame search for perlfunc, klick
it and search for upper.
> Maybe will be better to write some "OS independent", e.g. "look at
> function uc()".
> I don't know what type of documentation is on Mac.
I think the same as on Win. or Unix: perldoc and/or the HTML documentation.
regards,
Reinhard
--
------------------------------
Date: Fri, 05 Oct 2007 02:10:06 -0700
From: vocabulary <vocabulary49@gmail.com>
Subject: Re: optimal vs. optimized [was: Re: string concatentation...]
Message-Id: <1191575406.451002.276500@d55g2000hsg.googlegroups.com>
On Oct 2, 1:42 am, Michele Dondi <bik.m...@tiscalinet.it> wrote:
> Note: crossposted to some supposedly relevant groups. If anyone has
> better ones to suggest, then they're welcome.
>
> For people reading this outside of clpmisc, the question arose with
> the following post:
>
> <news:sfvqs4-b8b.ln1@osiris.mauzo.dyndns.org>
>
> which in turn was in response to an observation of mine. The whole
> thread is available from GG at the following URL:
>
> <http://groups.google.com/groups?threadm=3Dsfvqs4-b8b....@osiris.mauzo.dy=
ndns.org>
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=AD=3D=3D=3D=3D=3D
>
> On Thu, 27 Sep 2007 02:59:52 +0100, Ben Morrow <b...@morrow.me.uk>
> wrote:
>
> >You have a good point; however, as is usual in English grammar,
> >arguments from ancestry don't always help :). For instance, if 'optimum'
> >and derived words are necessarily superlative, then 'optimized' means
> >'made best', and A cannot be more optimized than B either. A has either
> >been 'made best' or it hasn't.
>
> I'm not sure. 'To optimize' could mean 'to try to reach the optimum'
> (or optimal incarnation - of something) thus 'optimized' may mean 'to
> have undergone the process of optimization', thus to have gone as much
> as possible (wrt some constraints, e.g. time) towards the optimum
> without necessarily reaching it. By contrast I see 'optimal' very much
> as a synonym of 'optimum' itself, and personally I find much more
> acceptable the expression 'more optimzed' than 'more optimal'.
>
> >I think what has happened is that, in English, 'optimal' and
> >'optimized' have acquired something of a sense of 'efficient', which is
> >clearly comparative, rather than of 'best' in a more general sense. So
>
> That they have been or are occasionally used in that sense may well
> be, but I would be surprised to learn that they have actually
> "acquired" it. If I paste the remaining two entries found by dict
> (which I snipped last time), namely:
>
> : From Moby Thesaurus II by Grady Ward, 1.0 :
> :
> : 24 Moby Thesaurus words for "optimal":
> : best, champion, choice, elect, elite, for the best, greatest,
> : handpicked, matchless, optimum, paramount, peerless, picked, prime,
> : prize, quintessential, select, supreme, surpassing, unmatchable,
> : unmatched, unparalleled, unsurpassed, very best
> : =20
> : =20
> :
> :
> : From The Free On-line Dictionary of Computing (27 SEP 03) :
> :
> : optimal
> : =20
> : 1. Describes a solution to a problem which
> : minimises some cost function. Linear programming is one
> : technique used to discover the optimal solution to certain
> : problems.
> : =20
> : 2. Of code: best or most efficient in time,
> : space or code size.
>
> you will see that the last one, which is specifically aimed at CS and
> IT -and it's actually relevant here- still does not mention just
> "efficiency". Thus my take on the issue is that 'optimal' is not just
> 'efficient' as alleged, but 'the most efficient'. All this, still at a
> syntactical level, i.e. we're not discussing yet what "efficient"
> could mean.
>
> I'll repeat myself: maybe this strikes me more strongly because of my
> implicit Latin heritage, but I still find 'more optimal' to sound like
> 'more most efficient'.
>
> >optimizing a program doesn't necessarily make it better, it simply makes
> >it more efficient: other things may be more important than efficiency,
>
> This is semantics. "better" and "more efficient" are both
> comparatives. That other things may be more important than efficiency
> (and indeed I think they are) is irrelevant to the linguistic point
> being discussed here.
>
> >portability or readability for example. 'Optimum' has not (I would say)
>
> We're not necessarily speaking of computer programs here, and although
> it is not in the dictionaries I mentioned before I think that the
> italian definition I found for 'ottimale' may well be translated in
> English, which is what I'm trying to do now:
>
> : adj: of something that, according to some determinate parameters or
> : points of view, represents the *best* possible condition or the *best*
> : possible result: e.g. optimal life conditions.
>
> If you accept this, then you can still speak in the context of
> programming of a
>
> >changed like this, so I find it odd that the dictionaries you quoted say
> >it is synonymous with 'optimal': I would entirely agree that 'more
> >optimum' is obviously wrong.
>
> In all earnestness I had never witnessed the use you're reporting of
> 'optimal', namely that in which it is not a superlative. But
> admittedly I do not read *that* much in English.
>
> >Theory aside, a quick google shows that 'more optimal' is definitely
> >acceptable usage; for instance (a random example from the results)
>
> Huh?!? Google may show that "ur so c00l bro" is acceptable usage!!
>
> > This is because the claim that A is more optimal or better adapted
> > than B with respect to some function does not entail that A is
> > optimal or even good with respect to that function.
>
> > http://www.seop.leeds.ac.uk/archives/fall1999/entries/teleology-biol=
ogy/
>
> >which shows that 'optimal' can have the sense of 'efficient' or
> >'effective' rather than simply 'best'.
>
> Well, that is from an academic institution thus should not fall in the
> "ur so c00l bro", but I'm still skeptical: young researchers, however
> good may they be in their research field, often tend to speak and
> write very bad in their own mother tongue. For example in Italy some
> young mathematicians are beginning to use the horrible anglophonic
> "surgettiva" in place of the traditional "suriettiva", not that a word
> borrowed from English is so bad in and of itself, but it is when
> there's a perfectly fine alternative in one's own language.
>
> > [English] not only borrows words from other languages; it has on
> > occasion chased other languages down dark alley-ways, clubbed them
> > unconscious and rifled their pockets for new vocabulary.
> > -- James Nicoll
>
> I knew that. In fact it's amongs my .sigs!
>
> Michele
> --
> {$_=3Dpack'B8'x25,unpack'A8'x32,$a^=3Dsub{pop^pop}->(map substr
> (($a||=3Djoin'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB=3D'
> .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=3D~/./g)x2,$_,
> 256),7,249);s/[^\w,]/ /g;$ \=3D/^J/?$/:"\r";print,redo}#JAPH,
Yes, vocabulary in English was made rich by the words from many other
languages. These languages were of the places where British and
English moved in the course of history. I saw a website which helps in
knowing words and building vocabulary. It is www.buildingvocabulary.org.
------------------------------
Date: Fri, 05 Oct 2007 01:14:52 GMT
From: "John W. Krahn" <dummy@example.com>
Subject: Re: perl join on a non printable variable character ?
Message-Id: <gegNi.145949$bO6.4584@edtnps89>
Jack wrote:
>
> On Oct 4, 1:46 pm, Sherman Pendley <spamt...@dot-app.org> wrote:
>>
>> Brian McCauley <nobul...@gmail.com> writes:
>>>
>>> Just to re-iterate (because I think I may have been unclear
>>> elsewhere), the following are all valid Perl but are very different
>>> statements.
>>> $delimiter=\034; # What you appear to claim you did
>>> $delimiter='\034'; # What you probably actually did
>>> $delimiter="\034"; # What you should have done
>>
>> On a related note - I'm not convinced that \034 is the correct character
>> to use. The OP mentioned using it as a field separator, and my Unicode
>> reference lists 034-037 as file, group, record, and unit separators, res-
>> pectively.
>
> sorry all, tried everything no luck here is the code. output should
> be : 1 ID TERM or put otherwise-
> rowcounter[nonprintabledelimiter]field1[nonprintabledelimiter]field2
> which is visible in the text file perl e:\add_uniquekeyfield.pl e:\tmp
> \file1.txt e:\tmp\file2.txt \034
You should put these two lines at the beginning of your Perl program to let
perl help you find mistakes:
use warnings;
use strict;
> if (@ARGV[0] eq undef) {
warnings enabled would have told you that using @ARGV[0] is wrong. Also, you
can't use the value of undef in a comparison like that, you want to use the
defined function instead:
if ( defined $ARGV[0] ) {
Or:
if ( not defined $ARGV[0] ) {
> $filename="no source filename" ;
> } else {
> $filename=@ARGV[0];
> }
>
> if (@ARGV[1] eq undef) {
> $outfilename="no dest filename" ;
> } else {
> $outfilename=@ARGV[1];
> }
> if (@ARGV[2] eq undef) {
> $delimiter="no dest filename" ;
> } else {
> $delimiter=@ARGV[2];
> }
You are passing the string '\034' to your program from the command line so
your $delimiter variable will contain the string consisting of the four
characters '\', '0', '3' and '4'.
> open(OUTFILE1,">$outfilename")|| die 'ERROR : external table not
> found :'.$outfilename."\n";
> open(SOURCE,$filename) || die 'ERROR : external table not found :'.
> $filename."\n";
You should include the $! variable in the error message so you know *why* it
failed.
> while (<SOURCE>) {
> chomp; #remove the newline from the line
> if (length($_) == 1 or length($_) == 0) { next; }; # skip the row
> # @temparray = split(/$delimiter/, $_); # works !!
When used in a regular expression the string '\034' is interpolated by the
string interpolater *and* the regular expression engine so it "works".
$ perl -le' $x = q[\034]; $test = qq[ one \034 two \\034 three ]; print for
split /$x/, $test'
one
two \034 three
> $rowcounter++;
> print OUTFILE1 join("$delimiter",$rowcounter,$_)."\n"; # doesnt work
> shoot me now !
When interpolated only by the string interpolater it is just a string.
$ perl -le' $x = q[\034]; print qq[ zero $x one \034 two \\034 three ];'
zero \034 one two \034 three
> print OUTFILE1 "$rowcounter$delimiter$_\n"; # no luck !
> } #end while
> # print $#temparray;
>
> close SOURCE;
> close OUTFILE1;
> close OUTFILE2;
John
--
Perl isn't a toolbox, but a small machine shop where you
can special-order certain sorts of tools at low cost and
in short order. -- Larry Wall
------------------------------
Date: Thu, 04 Oct 2007 18:58:08 -0700
From: Mintcake <tony@skelding.co.uk>
Subject: Re: perl join on a non printable variable character ?
Message-Id: <1191549488.195444.198170@g4g2000hsf.googlegroups.com>
On Oct 5, 6:51 am, Jack <jack_posem...@yahoo.com> wrote:
> On Oct 4, 1:46 pm, Sherman Pendley <spamt...@dot-app.org> wrote:
>
>
>
>
>
> > Brian McCauley <nobul...@gmail.com> writes:
> > > Just to re-iterate (because I think I may have been unclear
> > > elsewhere), the following are all valid Perl but are very different
> > > statements.
>
> > > $delimiter=\034; # What you appear to claim you did
> > > $delimiter='\034'; # What you probably actually did
> > > $delimiter="\034"; # What you should have done
>
> > On a related note - I'm not convinced that \034 is the correct character
> > to use. The OP mentioned using it as a field separator, and my Unicode
> > reference lists 034-037 as file, group, record, and unit separators, res-
> > pectively.
>
> > sherm--
>
> > --
> > Web Hosting by West Virginians, for West Virginians:http://wv-www.net
> > Cocoa programming in Perl:http://camelbones.sourceforge.net
>
> sorry all, tried everything no luck here is the code. output should
> be : 1 ID TERM or put otherwise-
> rowcounter[nonprintabledelimiter]field1[nonprintabledelimiter]field2
> which is visible in the text file perl e:\add_uniquekeyfield.pl e:\tmp
> \file1.txt e:\tmp\file2.txt \034
>
> if (@ARGV[0] eq undef) {
> $filename="no source filename" ;} else {
>
> $filename=@ARGV[0];
>
> }
>
> if (@ARGV[1] eq undef) {
> $outfilename="no dest filename" ;} else {
>
> $outfilename=@ARGV[1];}
>
> if (@ARGV[2] eq undef) {
> $delimiter="no dest filename" ;} else {
>
> $delimiter=@ARGV[2];
>
> }
>
> open(OUTFILE1,">$outfilename")|| die 'ERROR : external table not
> found :'.$outfilename."\n";
> open(SOURCE,$filename) || die 'ERROR : external table not found :'.
> $filename."\n";
>
> while (<SOURCE>) {
> chomp; #remove the newline from the line
> if (length($_) == 1 or length($_) == 0) { next; }; # skip the row
> # @temparray = split(/$delimiter/, $_); # works !!
> $rowcounter++;
> print OUTFILE1 join("$delimiter",$rowcounter,$_)."\n"; # doesnt work
> shoot me now !
> print OUTFILE1 "$rowcounter$delimiter$_\n"; # no luck !} #end while
>
> # print $#temparray;
>
> close SOURCE;
> close OUTFILE1;
> close OUTFILE2;- Hide quoted text -
>
> - Show quoted text -
At last - you've at least given enough information to indicate the
problem. Although several of the replies posted have more or less
identified the problem.
The three bits of useful information are:
1. 'passed in' means passed in from the command line
2. You're running on Windows (on *nix it would be different)
3. The value on the command line is a plain \034
The result is that $delimeter will be set to a 4 byte character string
comprising the characters '\', '0', '3', '4' rather than a single byte
string with the octal value 34.
You can check this yourself. On the command line type:
E:\perl -le "print $ARGV[0]" \034
\034
I'm not sure what wou'd have to enter on the Windows command line to
make it work. It may not even be possible. I'm not a great lover of
the windows CLI
If you really want the user to be able to specify the octal value of
the delimiter on the command line do something like...
$delimiter = chr oct $ARGV[2];
You can check this out on the command line, e.g.
E:\perl -le "print ord chr oct $ARGV[0]" 34
28
One other observation - did you really want the default value of the
delimiter to be "no dest filename"?
------------------------------
Date: Thu, 04 Oct 2007 20:38:38 -0700
From: Ron Bergin <rkb@i.frys.com>
Subject: Re: perl join on a non printable variable character ?
Message-Id: <1191555518.699665.17120@57g2000hsv.googlegroups.com>
On Oct 4, 4:51 pm, Jack <jack_posem...@yahoo.com> wrote:
>
> sorry all, tried everything no luck here is the code. output should
> be : 1 ID TERM or put otherwise-
> rowcounter[nonprintabledelimiter]field1[nonprintabledelimiter]field2
> which is visible in the text file perl e:\add_uniquekeyfield.pl e:\tmp
> \file1.txt e:\tmp\file2.txt \034
>
> if (@ARGV[0] eq undef) {
> $filename="no source filename" ;} else {
>
> $filename=@ARGV[0];
>
> }
>
> if (@ARGV[1] eq undef) {
> $outfilename="no dest filename" ;} else {
>
> $outfilename=@ARGV[1];}
>
> if (@ARGV[2] eq undef) {
> $delimiter="no dest filename" ;} else {
>
> $delimiter=@ARGV[2];
>
> }
>
> open(OUTFILE1,">$outfilename")|| die 'ERROR : external table not
> found :'.$outfilename."\n";
> open(SOURCE,$filename) || die 'ERROR : external table not found :'.
> $filename."\n";
>
> while (<SOURCE>) {
> chomp; #remove the newline from the line
> if (length($_) == 1 or length($_) == 0) { next; }; # skip the row
> # @temparray = split(/$delimiter/, $_); # works !!
> $rowcounter++;
> print OUTFILE1 join("$delimiter",$rowcounter,$_)."\n"; # doesnt work
> shoot me now !
> print OUTFILE1 "$rowcounter$delimiter$_\n"; # no luck !} #end while
>
> # print $#temparray;
>
> close SOURCE;
> close OUTFILE1;
> close OUTFILE2;
Several others have pointed out the main reasons why your script
fails, but I'll point out 1 or 2 other issues.
Your script requires 3 parameters, which you test for and assign a
default value, but "no dest filename" is a poor default to assign to
each param.
Even though 1 or more of the required params are missing, you still
proceed with the script. You really should exit with a usage
statement if any one of the required params are missing. You could do
something as simple as this:
if ( @ARGV != 3 || $ARGV[2] =~ /\D/ ) {
die "USAGE $0 [source file] [dest file] [delimiter]\n";
}
A better option would be to use the Getopt::Long or Getopt::Simple
module, in part, so that you don't need to worry about the order in
which the params are passed.
http://search.cpan.org/~rsavage/Getopt-Simple-1.48/lib/Getopt/Simple.pm
http://search.cpan.org/author/JV/Getopt-Long-2.37/lib/Getopt/Long.pm
------------------------------
Date: Fri, 5 Oct 2007 06:40:02 +0200
From: "Petr Vileta" <stoupa@practisoft.cz>
Subject: Re: perl join on a non printable variable character ?
Message-Id: <fe4fgk$1623$3@ns.felk.cvut.cz>
Jack wrote:
> Hi I am trying to join on decimal 28, or \034 the non printable field
> delimiter. I cant get this to work.. any help would be great ..
>
> assume $delimiter is passed in as \034
>
> works:
> @temparray = split(/$delimiter/, $_);
> @temparray = split(/\034/, $_);
> print OUTFILE1 join("\034",$rowcounter,$_)."\n";
>
> this doesnt work :
> print OUTFILE1 join("$delimiter",$rowcounter,$_)."\n";
> print OUTFILE1 join("\$delimiter",$rowcounter,$_)."\n";
> print OUTFILE1 join($delimiter,$rowcounter,$_)."\n";
> print OUTFILE1 join($$delimiter,$rowcounter,$_)."\n";
> or any variation of above ...
If you try it on Windows then you must use
binmode OUTFILE1;
before you write some to it.
If you use Linux or Mac then ignore me ;-)
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail. Send me your mail
from another non-spammer site please.)
------------------------------
Date: Fri, 05 Oct 2007 07:10:27 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <DrlNi.1167$lD6.264@newssvr27.news.prodigy.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 5 Oct 2007 06:36:08 +0200
From: "Petr Vileta" <stoupa@practisoft.cz>
Subject: Re: SIG{'PIPE'}
Message-Id: <fe4fgj$1623$2@ns.felk.cvut.cz>
Big and Blue wrote:
> Petr Vileta wrote:
>> I wrote some script to grab web pages, parse and store data to MySQL
>> database. On my local PC script work fine but on hosting server many
>> times fail for ungnown reason.
>
> One thing to bear in mind is that you can have a script that
> sometimes gets SIGPIPE and sometimes doesn't.
>
> As has been noted, it happens if you write to a closed pipe, e.g. a
> filehandle open by:
>
> open FH, "| command to run";
>
I checked my script and log written by script and I thing this is not a
reason. I use pipe only for send data to sendmail and this work already.
I'm not sure about LWP. Use LWP some pipes?
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail. Send me your mail
from another non-spammer site please.)
------------------------------
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 V11 Issue 907
**************************************
