[21869] in Perl-Users-Digest
Perl-Users Digest, Issue: 4073 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Nov 6 14:12:53 2002
Date: Wed, 6 Nov 2002 11:10:16 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Wed, 6 Nov 2002 Volume: 10 Number: 4073
Today's topics:
Perl module to read mails from Microsoft Outlook <mohammed@cse.unl.edu>
Re: Perl module to read mails from Microsoft Outlook (Helgi Briem)
Re: Perl module to read mails from Microsoft Outlook <djf@uk.xo.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
regex or substr or both? <lance@augustmail.com>
saving regex results <lance@augustmail.com>
Re: saving regex results <usenet@dwall.fastmail.fm>
Re: Simple question - What is unicode? <bart.lateur@pandora.be>
Re: Simple question - What is unicode? <bill.kemp@wire2.com>
Re: special characters in command-line (Stuart Kendrick)
Re: Telnet to OpenVMS, run cobol program - not working. <jozefn@newbolt.sonic.net>
Re: Telnet to OpenVMS, run cobol program - not working. <jozefn@newbolt.sonic.net>
Re: Textbooks on Perl/Python <melster@chello.no>
Re: Trapping System to System calls nobull@mail.com
Unix command ry@yokoyama.ws
Re: Unix command <graham.drabble@lineone.net>
Re: Unix command (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
Re: Unix command <usenet@dwall.fastmail.fm>
Re: Unix command <spam@thecouch.homeip.net>
Re: Unix command <ry@yokoyama.ws>
using Unicode::String to read a line from a file (ac)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 6 Nov 2002 15:32:25 GMT
From: Abid Mohammed <mohammed@cse.unl.edu>
Subject: Perl module to read mails from Microsoft Outlook
Message-Id: <aqbcm9$ekq$1@unlnews.unl.edu>
Hi,
I am trying to do the following and need some help. I have reports mailed to my mailbox(Microsoft Outlook)
which are put in a particular folder (say reports). I need to read the mails from the folder 'reports' parse
the data and project it in a two dimensional graph. Could any one let me know how to achieve this.
Thanks
------------------------------
Date: Wed, 06 Nov 2002 16:13:28 GMT
From: helgi@decode.is (Helgi Briem)
Subject: Re: Perl module to read mails from Microsoft Outlook
Message-Id: <3dc93dfd.1860975971@news.cis.dfn.de>
On 6 Nov 2002 15:32:25 GMT, Abid Mohammed
<mohammed@cse.unl.edu> wrote:
>I am trying to do the following and need some help. I have reports
>mailed to my mailbox(Microsoft Outlook) which are put in a
>particular folder (say reports).
perldoc -f opendir
perldoc -f grep
perldoc -f readdir
>I need to read the mails from the folder 'reports'
perldoc -f open
perldoc -f die
perldoc perlvar ($!)
>parse the data
Depends on the format but these are always useful:
perldoc -f split
perldoc perlre
perldoc -q balanced
>and project it in a two dimensional graph.
perldoc GD
http://search.cpan.org/author/LDS/GD-2.041/GD.pm
perldoc GD::Graph
http://search.cpan.org/author/MVERB/GDGraph-1.35/Graph.pm
>Could any one let me know how to achieve this.
--
Regards, Helgi Briem
helgi AT decode DOT is
A: Top posting
Q: What is the most irritating thing on Usenet?
- "Gordon" on apihna
------------------------------
Date: Wed, 6 Nov 2002 17:08:56 -0000
From: "djf" <djf@uk.xo.com>
Subject: Re: Perl module to read mails from Microsoft Outlook
Message-Id: <usij1npltp420d@corp.supernews.com>
"Abid Mohammed" <mohammed@cse.unl.edu> wrote in message
news:aqbcm9$ekq$1@unlnews.unl.edu...
> Hi,
>
> I am trying to do the following and need some help. I have reports mailed
to my mailbox(Microsoft Outlook)
> which are put in a particular folder (say reports). I need to read the
mails from the folder 'reports' parse
> the data and project it in a two dimensional graph. Could any one let me
know how to achieve this.
>
> Thanks
Doesn't Outlook put everything is a db style file, .pst I believe. I'm not
sure if attatchments are treated seperately unless manually extracted.
If thats the case - good luck
ps - I'd look at using a diff mail client if I was you - but thats just me !
------------------------------
Date: Wed, 06 Nov 2002 11:14:09 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.2 $)
Message-Id: <a46dnWnu-6980FSgXTWc2Q@august.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.2 $)
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.
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://mail.augustmail.com/~tadmc/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":
Please do not use the existence of these guidelines as a
"license to flame" or other meanness. It is possible that
a poster is not aware of the things discussed here. Let's
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" in the
very precise sense that they're used in technical conversation
(such as you're likely to 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 very unlikely that you're going to
get much benefit from using this group. We're not trying to boss
you around; we're just trying to convey the point without using
a lot 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 is expected regardless of what newsgroup
you are visiting. Lurking means to simply monitor a newsgroup for a
period of time until you become very familiar with local customs.
Think of a newsgroup as foreign culture. Each newsgroup has its own
specific customs and rituals. Get to know those customs and rituals
well before you participate. This will help you to 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.perl.com/CPAN-local/authors/Dean_Roehrich/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* the sections of quoted text
that your comments apply to. Failure to do this is called "Jeopardy"
posting because the answer comes before the question.
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://www.geocities.com/nnqweb/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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Wed, 06 Nov 2002 12:28:38 -0600
From: Lance Hoffmeyer <lance@augustmail.com>
Subject: regex or substr or both?
Message-Id: <pan.2002.11.06.18.28.38.162696.2546@augustmail.com>
given a file (test.txt):
line 1
line 2
line 3
Table 1
line 5
line 6
Male
10 25 35
line 9
Table 2
line 5
line 6
Female
11 35 45
line 9
I originally planed to create a series of regex's to find and extract
the number '35' from the file. Now I am wondering if using substr and
regex's would be better because I know that the number 35 (more
specifically, the second number on the line below 'Male') is always in
a substring below Table 1 and Male. What is the most efficient way
of handling this task: regex; substr; both; something else?
My original plan.
open(FILE,<gender.txt>);
series of regex to extract from line 8 the number 35
close(FILE);
Lance
------------------------------
Date: Wed, 06 Nov 2002 10:48:08 -0600
From: Lance Hoffmeyer <lance@augustmail.com>
Subject: saving regex results
Message-Id: <pan.2002.11.06.16.48.07.936122.2546@augustmail.com>
I am having some problems with simple rexex stuff.
Given a file:
NOthing on this line
Nothing on this line
Find this line 1
Table 167
Nothing on this line
Find this line 2
Nothing on this line
Nothing on this line
If I try
$target3 =~ m/TABLE.*/;
print $target3;
I expect "Table 167" to be printed but get nothing.
If I try:
if ($target1 =~ m/TABLE 167/){
$target2 =~ m/Find.*/)
}
print $target2;
I expect "Find this line 2" to be printed but get nothing
which I am certain has something to do with the previous
problem I am having (can't print Table 167).
Lance
------------------------------
Date: Wed, 06 Nov 2002 17:00:00 -0000
From: "David K. Wall" <usenet@dwall.fastmail.fm>
Subject: Re: saving regex results
Message-Id: <Xns92BE7A11EEC23dkwwashere@216.168.3.30>
Lance Hoffmeyer <lance@augustmail.com> wrote on 06 Nov 2002:
> I am having some problems with simple rexex stuff.
>
> Given a file:
>
> NOthing on this line
> Nothing on this line
> Find this line 1
> Table 167
> Nothing on this line
> Find this line 2
> Nothing on this line
> Nothing on this line
>
> If I try
> $target3 =~ m/TABLE.*/;
> print $target3;
>
> I expect "Table 167" to be printed but get nothing.
Don't expect that. :-)
Rather than just rewriting your code for you, here's where you can learn
for yourself:
perldoc perlrequick
perldoc perlretut
perldoc perlre
In perlrequick, look at the section "Extracting matches". In short: use
grouping parentheses and the dollar-number variables ($1, $2, ...).
--
David K. Wall - usenet@dwall.fastmail.fm
"Oook."
------------------------------
Date: Wed, 06 Nov 2002 14:32:46 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Simple question - What is unicode?
Message-Id: <jv9isuo6kb75rkbm648bmvl8cskfhcqdur@4ax.com>
David wrote:
>What is unicode *.txt?
<http://www.czyborra.com>
--
Bart.
------------------------------
Date: Wed, 6 Nov 2002 16:56:23 -0000
From: "W K" <bill.kemp@wire2.com>
Subject: Re: Simple question - What is unicode?
Message-Id: <PSby9.178$Xk3.1645@news.uk.colt.net>
Helgi Briem <helgi@decode.is> wrote in message
news:3dc91fdf.1853265264@news.cis.dfn.de...
> On Wed, 06 Nov 2002 13:46:11 GMT, "David"
> <erdstein@telstra.com> wrote:
>
> >What is unicode *.txt? There is an option to save a file in
> >this format in Excel.
>
> Unicode is a scheme for encoding alphabets other than
> the Latin by encoding each character with 2 bytes instead
> of 1. Perl 5.8 apparently has rather better unicode support
> than previous Perls.
And :
All latin-1 and ascii have the same numerical values in unicode, BUT are now
represented by two bytes instead of one.
The extra "blanks" are actually nulls. so "abc" in ascii is in hex - 41 42
43, in unicode it would be 00 41 00 42 00 43.
------------------------------
Date: 6 Nov 2002 10:11:24 -0800
From: skendric@fhcrc.org (Stuart Kendrick)
Subject: Re: special characters in command-line
Message-Id: <62dbf7f1.0211061011.45ead989@posting.google.com>
Hi John,
Ahh, I haven't noticed 'pipe' until now. I'll go play with that. Thanks!
--sk
------------------------------
Date: Wed, 06 Nov 2002 15:53:58 GMT
From: Joseph Norris <jozefn@newbolt.sonic.net>
Subject: Re: Telnet to OpenVMS, run cobol program - not working.
Message-Id: <Pine.LNX.4.40.0211060753060.28079-100000@newbolt.sonic.net>
Bob,
THanks for the help - I will give this a try.
#Joseph Norris (Perl - what else is there?/Linux/CGI/Mysql)
print @c=map chr $_+100,(6,17,15,16,-68,-3,10,11,16,4,1,14,-68,12,1,14,8,
-68,4,-3,-1,7,1,14,-68,-26,11,15,1,12,4,-68,-22,11,14,14,5,15,-90);
On Tue, 5 Nov 2002, Bob Walton wrote:
> Joseph Norris wrote:
>
>
> > I am using Net::Telnet to telnet into a OpenVms box and run a cobol
> > program. I have set the script up as below:
> >
> >
> > The problem is that the displays from the cobol program do not show
> > up and so my waitfor's do not make it and the script dies.
> >
> > The last entry in the log file just shows the name of the cobol program
> ...
>
>
> > $t->waitfor("PRINT ALL CLASSES? (DEFAULT ALL CLASSES)(Y/N)");
>
>
> Hmmmm...according to the docs, the single-string-argument waitfor is
> expecting a "matchop". That includes delimiters. So perhaps:
>
> $t->waitfor('/PRINT ALL CLASSES? (DEFAULT ALL CLASSES)(Y\/N)/');
>
> or maybe
>
> $t->waitfor('|PRINT ALL CLASSES? (DEFAULT ALL CLASSES)(Y/N)|');
>
> might work better? BTW, ' is recommended for quoting strings for
> matchops because of the hassles involved with some pattern
> metacharacters (like $) when dealing with " quotes. Quoting stuff in
> matchops gets a bit tricky. Perhaps you should just go for the string
> match, since you don't really need the regex match for what you are doing.
>
>
> ...
>
>
> > #Joseph Norris (Perl - what else is there?/Linux/CGI/Mysql)
>
> Cobol, apparently.
>
> ...
>
> --
> Bob Walton
>
------------------------------
Date: Wed, 06 Nov 2002 16:05:15 GMT
From: Joseph Norris <jozefn@newbolt.sonic.net>
Subject: Re: Telnet to OpenVMS, run cobol program - not working.
Message-Id: <Pine.LNX.4.40.0211060756590.28079-100000@newbolt.sonic.net>
Bob,
One other thing that I should mention. It appears that I am not even
running the program. The log file shows no display statements at all.
The last statement is the run of the cobol statement and then it appears
to be no interaction after that.
Here is what the code looks like with a test script:
use Net::Telnet ();
$username = 'username';
$passwd = 'userpass';
$filename = 'telnet.log';
unlink $filename;
$t = new Net::Telnet (Timeout => 60);
$fh = $t->dump_log;
$fh = $t->dump_log($fh);
$fh = $t->dump_log($filename);
print "dump set\n";
$t->open("10.1.1.1"); # number changed to protect the guilty
print "at open\n";
$t->login(Name=>$username, Password=>$passwd, Prompt=>'/\$/');
print "at dir cmd\n";
# the simple cobol program below does just two displays
# I am not catching these at all in my getlines.
# it just shows the run statement in the log and nothing after that.
$t->print(" run cobtest.exe");
@lines = $t->getlines;
$t->print("logout");
$t->close;
my $cnt = 0;
for (@lines){
$cnt++;
print "$cnt: $_\n";
}
exit(0);
#Joseph Norris (Perl - what else is there?/Linux/CGI/Mysql)
print @c=map chr $_+100,(6,17,15,16,-68,-3,10,11,16,4,1,14,-68,12,1,14,8,
-68,4,-3,-1,7,1,14,-68,-26,11,15,1,12,4,-68,-22,11,14,14,5,15,-90);
On Tue, 5 Nov 2002, Bob Walton wrote:
> Joseph Norris wrote:
>
>
> > I am using Net::Telnet to telnet into a OpenVms box and run a cobol
> > program. I have set the script up as below:
> >
> >
> > The problem is that the displays from the cobol program do not show
> > up and so my waitfor's do not make it and the script dies.
> >
> > The last entry in the log file just shows the name of the cobol program
> ...
>
>
> > $t->waitfor("PRINT ALL CLASSES? (DEFAULT ALL CLASSES)(Y/N)");
>
>
> Hmmmm...according to the docs, the single-string-argument waitfor is
> expecting a "matchop". That includes delimiters. So perhaps:
>
> $t->waitfor('/PRINT ALL CLASSES? (DEFAULT ALL CLASSES)(Y\/N)/');
>
> or maybe
>
> $t->waitfor('|PRINT ALL CLASSES? (DEFAULT ALL CLASSES)(Y/N)|');
>
> might work better? BTW, ' is recommended for quoting strings for
> matchops because of the hassles involved with some pattern
> metacharacters (like $) when dealing with " quotes. Quoting stuff in
> matchops gets a bit tricky. Perhaps you should just go for the string
> match, since you don't really need the regex match for what you are doing.
>
>
> ...
>
>
> > #Joseph Norris (Perl - what else is there?/Linux/CGI/Mysql)
>
> Cobol, apparently.
>
> ...
>
> --
> Bob Walton
>
------------------------------
Date: Wed, 06 Nov 2002 18:12:45 GMT
From: "Martin Elster" <melster@chello.no>
Subject: Re: Textbooks on Perl/Python
Message-Id: <xYcy9.29$Ig5.1030@news01.chello.no>
Jalab wrote:
> Greetings all,
> Any help in finding a university level textbook on the subject of
> "Scripting languages" I am mainly looking for a book that covers Perl
> and Python only as the 2 main scripting languages and that is written
> for students, i.e. chapter summary, exercises, etc. I hate to force my
> student to buy and study from two separate books.
>
> Any ideas?
At the University of Oslo there is currently a course which teaches
Python, Perl and some Bash. The professor, H. P. Langtangen, has written
a textbook called "Scripting Tools for Scientific Computations". The
book hasn't been published yet, but there exists a preliminary version
which the students are using. I like it. You might want to check out the
course homepage (in Norwegian):
http://www.ifi.uio.no/in228/
or take a look at the course notes (in English), which cover alot and
will give you a good idea of what the book is like:
http://www.ifi.uio.no/in228/lecsplit/index.html
If this seems interesting I suggest you get in touch with the
professor/author. You'll find his email address at the course homepage.
Good luck.
Martin
------------------------------
Date: 6 Nov 2002 10:47:44 -0800
From: nobull@mail.com
Subject: Re: Trapping System to System calls
Message-Id: <4dafc536.0211061047.474a428@posting.google.com>
amarsantpur@hotmail.com (amar) wrote in message news:<51db1bd3.0211060256.412a37df@posting.google.com>...
> What i
> am trying to say is i have a script which dumps a shell script and i
> do a system of that script. This shell script in turns calls another
> executable (perl script) which has system calls present in it. Now if
> that executable doesnt get executed properly is it possible for my
> script to get hold of the reasons for the failure of that executable.
It is not possible to get directly at the exit stauts of your
grandchildren, you must make the child propagate this information.
> Or is it possible to know that this executable has not run properly
> due to some problems. if i do $? of the system call i am using in my
> script it says it has passed. But that executable has not run. Can
> anyone of you
> suggest me is there any way of catching this error.
I suspect that you are looking for the "abort on error" feature of
shell.
In bash this is -e. I think it's part of POSIX /bin/sh too.
This, of course, has nothing to do with Perl.
------------------------------
Date: Wed, 06 Nov 2002 16:28:41 GMT
From: ry@yokoyama.ws
Subject: Unix command
Message-Id: <MPG.18330e03d4e586ff98968d@news-server.nyc.rr.com>
Hello All!
Is it possible to invoke unix command from Perl? If so, please tell me
how.
Thanks in advance.
------------------------------
Date: Wed, 06 Nov 2002 16:44:23 GMT
From: Graham Drabble <graham.drabble@lineone.net>
Subject: Re: Unix command
Message-Id: <Xns92BEAA49140DEgrahamdrabblelineone@ID-77355.user.dfncis.de>
On 06 Nov 2002 ry@yokoyama.ws wrote in
news:MPG.18330e03d4e586ff98968d@news-server.nyc.rr.com:
> Hello All!
>
> Is it possible to invoke unix command from Perl? If so, please
> tell me how.
perldoc -f system
perldoc -f exec
--
Graham Drabble
If you're interested in what goes on in other groups or want to find
an interesting group to read then check news.groups.reviews for what
others have to say or contribute a review for others to read.
------------------------------
Date: 06 Nov 2002 17:39:46 +0100
From: mru@users.sourceforge.net (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=)
Subject: Re: Unix command
Message-Id: <yw1xel9yzm7h.fsf@plopp.e.kth.se>
ry@yokoyama.ws writes:
> Is it possible to invoke unix command from Perl? If so, please tell me
> how.
perldoc -f system
--
Måns Rullgård
mru@users.sf.net
------------------------------
Date: Wed, 06 Nov 2002 16:49:49 -0000
From: "David K. Wall" <usenet@dwall.fastmail.fm>
Subject: Re: Unix command
Message-Id: <Xns92BE785853E07dkwwashere@216.168.3.30>
<ry@yokoyama.ws> wrote on 06 Nov 2002:
> Is it possible to invoke unix command from Perl? If so, please tell me
> how.
perldoc -q "external command"
------------------------------
Date: Wed, 06 Nov 2002 11:59:16 -0500
From: Mina Naguib <spam@thecouch.homeip.net>
Subject: Re: Unix command
Message-Id: <3DC94A64.2060906@thecouch.homeip.net>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
ry@yokoyama.ws wrote:
| Hello All!
|
| Is it possible to invoke unix command from Perl? If so, please tell me
| how.
|
| Thanks in advance.
By reading the manual. Look into the system() command.
-----BEGIN xxx SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9yUpkeS99pGMif6wRAk3HAJ9G/Csrz/NNtXsMc5ya6NH1PyeaugCdGfvp
CAN+iVwIeihTonIng4jrsak=
=33Di
-----END PGP SIGNATURE-----
------------------------------
Date: Wed, 06 Nov 2002 17:32:22 GMT
From: <ry@yokoyama.ws>
Subject: Re: Unix command
Message-Id: <MPG.18331c65b11f839498968e@news-server.nyc.rr.com>
Thanks for people answering my question. I did not konw perldoc. I
will read it.
I have another question. Is there FAQ? If so, could you tell me where I
can find it.
Thanks
In article <MPG.18330e03d4e586ff98968d@news-server.nyc.rr.com>,
ry@yokoyama.ws says...
> Hello All!
>
> Is it possible to invoke unix command from Perl? If so, please tell me
> how.
>
> Thanks in advance.
>
>
>
------------------------------
Date: 6 Nov 2002 06:53:08 -0800
From: aclarke@austin.rr.com (ac)
Subject: using Unicode::String to read a line from a file
Message-Id: <ec432b9c.0211060653.476bf6cb@posting.google.com>
My current application reads from text files like so:
while (my $line = <INPUT>)
{
...
}
Note that its line-oriented. I now need to update it to "sort of
handle" Unicode-based text files. The "sort of" is that I have some
wiggle room in that its acceptable to "lose data" by converting it to
ANSI (latin1, etc).
I was looking at Unicode::String. It looks pretty good. But I have
some questions.
1. How do I write the loop above using a Unicode::String (ie,
preserving the line-oriented reading)?
2. How can I tell that I'm dealing with a Unicode file?
3. Can I write the logic so that it will work with either an ANSI file
or a Unicode file?
I appreciate comments on this.
Allan
------------------------------
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.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 4073
***************************************
