[31850] in Perl-Users-Digest
Perl-Users Digest, Issue: 3113 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Sep 3 06:09:21 2010
Date: Fri, 3 Sep 2010 03:09:06 -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, 3 Sep 2010 Volume: 11 Number: 3113
Today's topics:
Re: Multidimensional array <justin.1007@purestblue.com>
Re: Multidimensional array <paul@pstech-inc.com>
Re: Multidimensional array <jurgenex@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Regex help <hara.acharya@gmail.com>
Re: Regex help <jurgenex@hotmail.com>
Re: Regex help <uri@StemSystems.com>
Re: Regex help <bugbear@trim_papermule.co.uk_trim>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 3 Sep 2010 09:40:52 +0100
From: Justin C <justin.1007@purestblue.com>
Subject: Re: Multidimensional array
Message-Id: <kto6l7-am8.ln1@zem.masonsmusic.co.uk>
On 2010-09-02, Paul E. Schoen <paul@pstech-inc.com> wrote:
>
> I'm stuck once again. I want to be able to store a hash of events sorted by
> Date (or perhaps DateTime) in a text file, and read back into the hash where
> I can add new events or delete old ones. The hash is defines as:
>
> my %Event_DB = (
> $E_Date => {
> Date => $E_Date, #This was previously an array
> Time => $E_Time,
> Title => $E_Title,
> Descr => $E_Descr,
> },
> );
>
> I am storing the data received from the HTML form as follows:
>
> my $filename = "events.txt";
>
> #*** Can't create file in cgi-bin; must create empty file and chmod 777
> #unless (-e $filename) { #check for exist
> open (EventFile, '>>', $filename)
> or HTMLdie ("File write error: $!");
>
> for my $event (map $Event_DB{$_}, sort keys %Event_DB) {
> print (EventFile $event->{Title});
> print (EventFile $event->{Date});
> print (EventFile $event->{Time});
> print (EventFile $event->{Descr});
> }
> close (EventFile);
> # }
>
Try 'Learning Perl' ch17 seeing as you appear to have access to the Perl
CD Bookshelf.
> http://docstore.mik.ua/orelly/perl/cookbook/ch11_15.htm
Is this a legitimate way to access the Perl CD Bookshelf?
Justin.
--
Justin C, by the sea.
------------------------------
Date: Fri, 3 Sep 2010 05:20:39 -0400
From: "Paul E. Schoen" <paul@pstech-inc.com>
Subject: Re: Multidimensional array
Message-Id: <T53go.20147$8A2.19764@newsfe22.iad>
"Uri Guttman" <uri@StemSystems.com> wrote in message
news:8762yneqwg.fsf@quad.sysarch.com...
>>>>>> "PES" == Paul E Schoen <paul@pstech-inc.com> writes:
>
> PES> Maybe I should uninstall the DotCMS host and install an Apache
> server?
>
> yes, yes, and YES. no reason to use anything but apache. you can do so
> many things on your own and not need your external web host for anything
> but production.
The server that will most likely host this is Apache. But as mentioned
elsewhere setting it up is non-trivial and one more thing I don't want to
mess with at this point. I can run the script locally but I had to use goto
statements to spaghetti code around the CGI stuff and simulate the data from
the HTML page.
Maybe there is a way to detect that there is no CGI data and provide the
simulated stuff without having to change the source code for local or remote
(live server?) use.
I have finally achieved most of my goal for this script, and I am now using
a DBI database connection. It seems much easier to me than using hashes and
worrying about data separators and \n newlines in some fields. Here is
roughly what I've done:
use warnings;
use strict;
use DBI;
use Fcntl;
use DateTime;
... Get CGI data and mail a copy to me
my $E_Date = $in{'Event_Date'}; #Date in yyyymmdd format
my $E_Time = $in{'Event_Time'}; #Time in hh:mm format
my $E_Title = $in{'Event_Title'};
my $E_Descr = $in{'Event_Description'}; #Description may have newlines
#This will replace the $E_Date and $E_Time; using "now" to simulate
my $E_DT = DateTime->now;
my $dbfile = "events.db";
my $db = DBI->connect( # connect to your database, create if
needed
"dbi:SQLite:dbname=$dbfile", # DSN: dbi, driver, database file
"", # no user
"", # no password
{ RaiseError => 1, AutoCommit => 1 } # complain if something goes wrong
) or die $DBI::errstr;
unless (-e $dbfile) { #check for exist
$db->do("CREATE TABLE tEvents (dt DATETIME PRIMARY KEY, tl TEXT, de
TEXT)");
}
$db->do("PRAGMA foreign_keys = OFF");
$db->do("INSERT INTO tEvents (dt,tl,de) VALUES ('$E_DT', '$E_Title',
'$E_Descr')");
my $all = $db->selectall_arrayref("SELECT * FROM tEvents");
# Print the data for debugging purposes
foreach my $row (@$all) {
($E_DT, $E_Title, $E_Descr) = @$row;
my @dt = split('T',$E_DT); #I tried using $E_DT->mdy with no joy
my $d = $dt[0]; #Extract the date portion yyyy-mm-dd
my $t = $dt[1]; #Extract the time portion hh:mm:ss
print "$E_Title\n$d $t\n$E_Descr\n";
}
# Print the data in HTML to the user
[snip]
# Print to the HTML file (write, append, create)
# Yes I know I need to change the HTML format
open (DATA1, '>', "output.htm")
or HTMLdie ("File error: $!");
print DATA1 <<EOF ;
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>iframe - Events - Greater Baltimore Group Sierra Club Web
Site</title>
</head>
<body>
<h1>Events</h1><hr>
EOF
foreach my $row (@$all) {
($E_DT, $E_Title, $E_Descr) = @$row;
my @dt = split('T',$E_DT);
my $d = $dt[0];
my $t = $dt[1];
print DATA1 "<p><h3>$E_Title</h3>\n";
print DATA1 "<h4>$d $t</h4>\n";
print DATA1 "$E_Descr<hr>\n";
}
print DATA1 <<EOF ;
</body>
</html>
EOF
close (DATA1);
That's about all there is to it, for now. I need to clean up some things but
it seems to do the job, and it was a learning experience. I can see how
powerful Perl is and how it may be convenient for the language to take care
of the low-level details and use adaptive context so that types need not be
declared, but it's still confusing and frustrating for me. I've spent many
late-late hours on this and most of that was learning how to do relatively
simple things, and also dealing with as yet unknown problems such as the
inability to use the datetime format functions, and also why the interpreter
would sometimes give an error of table tEvents not found.
Many thanks to all who have helped me with this. Hopefully I can now get
busy with some of the other details to make this useful and secure. I will
definitely need to store the database and HTML files someplace other than
the cgi-bin directory. The webmaster for the Sierra Club says their server
does not support CGI so I will need to host that part myself.
Up until now all events were submitted to the webmasters of the various
chapters and local groups and they had to update the content. I think our
Greater Baltimore Group's site has been maintained manually and the events
were often delayed by weeks or months. The other sites that we might want to
emulate appear to use a CMS of some kind, and for a while I used Atomz for
the Maryland site, but I found it difficult to use, and now I think Atomz is
no longer available.
Here are the websites mentioned:
http://maryland.sierraclub.org
http://maryland.sierraclub.org/baltimore I have placed links here to the
live event submission form and the new site under construction
http://maryland.sierraclub.org/Montgomery I used this site as a template
for the one under construction
http://maryland.sierraclub.org/Catoctin I might use this model instead,
as it seems simpler and it fills the entire width of the screen
Paul
------------------------------
Date: Fri, 03 Sep 2010 02:41:40 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Multidimensional array
Message-Id: <jbg18695fd08g0nfb7h1l5j3tm8eq9g9fr@4ax.com>
"Paul E. Schoen" <paul@pstech-inc.com> wrote:
>The server that will most likely host this is Apache. But as mentioned
>elsewhere setting it up is non-trivial and one more thing I don't want to
>mess with at this point. I can run the script locally but I had to use goto
>statements to spaghetti code around the CGI stuff and simulate the data from
>the HTML page.
???
You did read the section "DEBUGGING" in "perldoc CGI", didn't you?
DEBUGGING
If you are running the script from the command line or in the perl
debugger, you can pass the script a list of keywords or
parameter=value
pairs on the command line or from standard input [...]
>Maybe there is a way to detect that there is no CGI data and provide the
>simulated stuff without having to change the source code for local or remote
>(live server?) use.
Yes, as documented in the documentaton of the tool you are using.
>I have finally achieved most of my goal for this script, and I am now using
>a DBI database connection. It seems much easier to me than using hashes and
Hashes are not that bad. Just think of them as arrays that use text
instead of numbers as indices.
jue
------------------------------
Date: Fri, 03 Sep 2010 02:16:51 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <XdydneMBh7N-PR3RnZ2dnUVZ5oidnZ2d@giganews.com>
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.9 $)
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_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.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Thu, 2 Sep 2010 21:42:46 -0700 (PDT)
From: king <hara.acharya@gmail.com>
Subject: Regex help
Message-Id: <4b0a3e3c-adfe-4b8c-985d-1c369952fd93@m35g2000prn.googlegroups.com>
I have a script as below.
"
#!/c/perl/bin
system("typeperf \"\\Processor\(\*\)\\% C1 Time\" -sc 1 > C1.txt");
system("typeperf \"\\Processor\(\*\)\\% C2 Time\" -sc 1 > C2.txt");
system("typeperf \"\\Processor\(\*\)\\% C3 Time\" -sc 1 > C3.txt");
sleep 1;
#open(C1,"C1.txt");
#$C1_ARR=<C1>;
#close(C1);
open C1, "<C1.txt";
$C1_CONTENT = do { local $/; <C1> };
print "$C1_CONTENT\n";"
Now in the $C1_CONTENT the content is as below.
""(PDH-CSV 4.0)","\\Test_PC\Processor(0)\% C1 Time","\\HACHARYX-MOBL
\Processor(1)\% C1 Time","\\HACHARYX-MOBL\Processor(_Total)\% C1 Time"
"09/03/2010 09:58:36.052","9.797092","11.412473","10.604782"
Exiting, please wait...
The command completed successfully."
I am trying to find a regex so that I can extract the exact three
values from the scalar and put in different variables and do some
operation. I want to keep finding values repeatably and values varies
but will be in same format. In this case the values are:
"9.797092","11.412473","10.604782"
Can anybody help in this.
------------------------------
Date: Thu, 02 Sep 2010 21:57:36 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Regex help
Message-Id: <msv0869trjtgrgd2t376dteetrcf76fqfh@4ax.com>
king <hara.acharya@gmail.com> wrote:
>Now in the $C1_CONTENT the content is as below.
>""(PDH-CSV 4.0)","\\Test_PC\Processor(0)\% C1 Time","\\HACHARYX-MOBL
>\Processor(1)\% C1 Time","\\HACHARYX-MOBL\Processor(_Total)\% C1 Time"
>"09/03/2010 09:58:36.052","9.797092","11.412473","10.604782"
Baring any line breaks in this posting this very very much looks like a
CSV file.
>Exiting, please wait...
>The command completed successfully."
>
>I am trying to find a regex so that I can extract the exact three
If this is a CSV file format then why are you trying to do it the hard
way? Just use a parser for CSV files, grap the 6th, 7th, and 8th element
and be done with it.
jue
------------------------------
Date: Fri, 03 Sep 2010 01:09:21 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Regex help
Message-Id: <87aanz8lby.fsf@quad.sysarch.com>
>>>>> "k" == king <hara.acharya@gmail.com> writes:
k> I have a script as below.
k> #!/c/perl/bin
k> system("typeperf \"\\Processor\(\*\)\\% C1 Time\" -sc 1 > C1.txt");
k> system("typeperf \"\\Processor\(\*\)\\% C2 Time\" -sc 1 > C2.txt");
k> system("typeperf \"\\Processor\(\*\)\\% C3 Time\" -sc 1 > C3.txt");
learn how to use alternate delimiters. hell, that could just be done
with single quotes as i see no interpolation. the backwhacks makes it
impossible to read.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Fri, 03 Sep 2010 09:22:37 +0100
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: Regex help
Message-Id: <Od2dne24nrjTLR3RnZ2dnUVZ8tednZ2d@brightview.co.uk>
Uri Guttman wrote:
>>>>>> "k" == king <hara.acharya@gmail.com> writes:
>
> k> I have a script as below.
> k> #!/c/perl/bin
> k> system("typeperf \"\\Processor\(\*\)\\% C1 Time\" -sc 1 > C1.txt");
> k> system("typeperf \"\\Processor\(\*\)\\% C2 Time\" -sc 1 > C2.txt");
> k> system("typeperf \"\\Processor\(\*\)\\% C3 Time\" -sc 1 > C3.txt");
>
> learn how to use alternate delimiters. hell, that could just be done
> with single quotes as i see no interpolation. the backwhacks makes it
> impossible to read.
And use pipe (open) not temp files...
BugBear
------------------------------
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 3113
***************************************
