[19475] in Perl-Users-Digest
Perl-Users Digest, Issue: 1670 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Aug 31 14:10:31 2001
Date: Fri, 31 Aug 2001 11:10:13 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <999281413-v10-i1670@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Fri, 31 Aug 2001 Volume: 10 Number: 1670
Today's topics:
Re: NT Query nobull@mail.com
Open 2 exes from Perl (George K)
Re: perl and oracle (Hardy Merrill)
Re: Perl editor for win32 needed (Chris Harris)
Perl script calling shell script failing (Google_Don)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Programming sockets <Crazydj@web.de>
Re: registration worries (Mark Jason Dominus)
Running multiple procedures simultaneously <akirby@wharton.upenn.edu>
Thanks <jclover@nati.org>
Re: Using perl for a server daemon????? <bseib@jade.cc.purdue.edu>
Re: Weird -w behaviour (Benoit Gauthier)
Which modules have I added? <jcook@strobedata.com>
Re: Which modules have I added? <ronh@iainc.com>
Re: Which modules have I added? (Mark Jason Dominus)
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 31 Aug 2001 18:33:58 +0100
From: nobull@mail.com
Subject: Re: NT Query
Message-Id: <u9vgj49lrt.fsf@wcl-l.bham.ac.uk>
<e2e4@pacbell.net> writes:
> I'm trying to connnect to a server on our network remotely, and get a list
> of all the active users for use in a perl script (for the boss). I can look
> at the server using PerfMon, but don't see how to get the list of users into
> a script. Anyone know?
You mean you are able to get this information via PerfMon?
I didn't think this information actually existed at all in the NT
world!
The nearest I've ever managed to do was a Perl script that connected
to the server and searched backwards through the Security event log
(back as far as the last system reboot event) and reported any login
event that wasn't matched by a logout event.
Of course this can give both false positives and false negatives.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: 31 Aug 2001 10:33:11 -0700
From: gkdata@cs.com (George K)
Subject: Open 2 exes from Perl
Message-Id: <5b5f48f5.0108310933.1b78a448@posting.google.com>
I am running Windoz 2000 and ActivePerl 5.6 (this is my work box - at
home I run RH :)
I am trying to do the following 2 things from one script:
- change the current directory of my command window to another
directory
- open Win Notepad.exe
The closest I've come is
system ('c:\winnt\notepad.exe');
system ('%SystemRoot%\system32\cmd.exe');
wait();
BUT I have many issues!
The main problem is that while I can open Notepad I lose the command
window- it freezes up with no cursor. It seems like it is waiting for
Notepad to finish. As a matter of fact, when I close Notepad, the
cursor reappears in the command window.
So my question is : is it possible to call and run two seperate exe
files from a single perl script? If so, could you point me to the
proper docs so I can learn how? (I'd rather learn myself than have you
GIVE me the answer.)
Any ides would be greatly appreciated.
------------------------------
Date: 31 Aug 2001 10:17:45 -0700
From: merrill@missioncriticallinux.com (Hardy Merrill)
Subject: Re: perl and oracle
Message-Id: <fdfedf4b.0108310917.d084cc5@posting.google.com>
Philippe PERRIN <philippe.perrin@sxb.bsf.alcatel.fr> wrote in message news:<3B8F4E94.55317394@sxb.bsf.alcatel.fr>...
> "Manuel Körner" wrote:
> > The perlcode looks like:
> > my $sth=$dbh->prepare("insert into table values(?,?,?));
> > $sth->execute("sequence.nextval", "test", "sysdate");
> > I know the quotes for "sequence.nextval" and "sysdate" are wrong.
>
> I use a command string like :
> "insert into table values(seq_commande.nextval,$num_cl,SYSDATE,$type)"
>
> So I use Oracle's SYSDATE function, instead of Perl.
> And it works fine (with me :-)
I don't think you can use placeholders in place of SYSDATE or
sequence.nextval - those 2 things need to be *in* the actual sql. I
tried using them with placeholders like you, but I couldn't get them
to work.
Here's yours:
my $sth=$dbh->prepare("insert into table values(?,?,?));
$sth->execute("sequence.nextval", "test", "sysdate");
Here's what I think you will need:
my $sth=$dbh->prepare(qq{
insert into table
values (sequence.nextval, ?, sysdate)
});
$sth->execute("test");
HTH
--
Hardy Merrill
Mission Critical Linux, Inc.
http://www.missioncriticallinux.com
------------------------------
Date: Fri, 31 Aug 2001 16:45:11 GMT
From: clh8762@hotmail.com (Chris Harris)
Subject: Re: Perl editor for win32 needed
Message-Id: <3b8fbef3.160781001@news.networktel.net>
On Tue, 07 Aug 2001 10:09:17 GMT, "Nikolas Garofil"
<nikolas_garofil@hotmail.com> wrote:
>What is the best editor to write perl scripts in Windows 98
>
>
SciTE
http://www.scintilla.org
Chris
------------------------------
Date: 31 Aug 2001 09:31:23 -0700
From: dvmak@att.net (Google_Don)
Subject: Perl script calling shell script failing
Message-Id: <74d22f15.0108310831.263d93ed@posting.google.com>
I have a dynamic web page that on Post calls a perl script. This is
used for uploading files from a PC to a server. In the perl script I
call a shell script that ftp's the file to another server. (If we had
NET:FTP installed I'd use that)
When all is done the perl script calls another web page where the
status is displayed.
The problem:
The file does get created and the ftp succeeds, the url is built for
return but I keep getting the Apache Internal server error and the log
shows:
<ip cut> malformed header from script. Bad header=File Transfer
Successful <dir cut>
If I remark out the actual system call all is fine.
Something with the display of the output and return from the shell
script that perl doesn't like. What am I missing here?
Thanks
------------------------------
Date: Fri, 31 Aug 2001 17:33:56 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.2 $)
Message-Id: <8UPj7.34126$4b5.855678@news6.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.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: Fri, 31 Aug 2001 17:22:33 +0200
From: Crazydj <Crazydj@web.de>
Subject: Re: Programming sockets
Message-Id: <3B8FABB9.38BAD8E2@web.de>
Ronald Blaschke schrieb:
> On Fri, 31 Aug 2001 16:33:07 +0200, Crazydj <Crazydj@web.de> wrote:
> > Ronald Blaschke schrieb:
> >
> > > A good metaphor when thinking about TCP is a telephone line. So, when
> > > you call someone and he picks up the line, how does he know how to
> > > talk to you? :-)
> > >
> > > I'd recommend using Net::SMTP to send an email, especially if you are
> > > not too TCP and SMTP wary.
> > >
> > > If you absolutely have to do it yourself, here are some hints:
> [ hints removed ]
> > >
> > > Don't know where to find a good tutorial. I can recommend a book
> > > or two, though.
> > >
> > O.K I have got it, just read from the created socket ;-p
> > But I have still the problem that the SMTP server doesn't get my DATA command...
> >
> > Here is my newest version of that script:
> >
> [ script removed ]
>
> Just ran your script and it worked fine for me. Output follows.
> ----------
> Connected.
> 220 localhost ESMTP Exim 3.12 #1 Fri, 31 Aug 2001 16:43:38 +0200
>
> 250 localhost Hello rb at localhost [127.0.0.1]
>
> 250 <perllover@crazydj.de> is syntactically correct
>
> 250 <rb@localhost> is syntactically correct
>
> 354 Enter message, ending with "." on a line by itself
> ---------
>
> Could you give me more details regarding your problem? Error msg, etc.
> --
Sorry, but I recognized that there is no problem, the mail was send...
...but I was wondering why I didn't saw the answer "Message accepted for delivery".
...I have just not read enough from the socket :-(
--
Djz rule the world! ...and some other staff ;-p Find out at http://www.crazydj.de
------------------------------
Date: Fri, 31 Aug 2001 17:00:19 GMT
From: mjd@plover.com (Mark Jason Dominus)
Subject: Re: registration worries
Message-Id: <3b8fc2a2.2b51$38c@news.op.net>
In article <5370f8aa.0108310608.e48069d@posting.google.com>,
Mr. Green <greenseaweed@aol.com> wrote:
>Very helpful. Thanks. But I wonder if it would be more efficient to
>ditch the random method and simply count the total number of files in
>the directory and then let the file name be the total number plus one.
You mean you want the total number plus one thousand.
On average the efficiency is the same.
I left in the random generation because I thought you might have had a
reason for putting it in, that you actually *wanted* random filenames.
--
@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($q*=2)+=$f=!fork;map{$P=$P[$f^ord
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^[P.]/&&
close$_}%p;wait until$?;map{/^r/&&<$_>}%p;$_=$d[$q];sleep rand(2)if/\S/;print
------------------------------
Date: Fri, 31 Aug 2001 12:20:48 -0400
From: "Adam Kirby" <akirby@wharton.upenn.edu>
Subject: Running multiple procedures simultaneously
Message-Id: <9modfp$43s$1@netnews.upenn.edu>
I have a program which basically runs 5 searches (seperate procedures) one
right after the other. I'd like to speed the program up considerably by
running these searches at the same time. How would I go about doing this.
Since they're in the same program, can I use fork? These procedures do
access global variables.
Thanks in advance!
Adam Kirby
------------------------------
Date: Fri, 31 Aug 2001 11:03:47 -0500
From: "Jonathan Clover" <jclover@nati.org>
Subject: Thanks
Message-Id: <tovculhd29fl03@corp.supernews.com>
Thanks all!
Jonathan
"Jonathan Clover" <jclover@nati.org> wrote in message
news:tov8vu1bmc4maf@corp.supernews.com...
> I have this code to insert a new row into a database and I would like to
> make the code, that's focused on(!) more concise, but am unsure on how.
> Ideas anyone.
> Jonathan Clover
> NATI
>
> P.S. @question will always and only contain 10 values
>
> my $dbh = DBI->connect("DBI:CSV:f_dir=$database_dir")
> or diehtml("Cannot connect: " . $DBI::errstr);
>
> ! $dbh->do( "insert into test_ans values
>
('$test','$questions[0]','$questions[1]','$questions[2]','$questions[3]','$q
>
uestions[4]','$questions[5]','$questions[6]','$questions[7]','$questions[8]'
> ,'$questions[9]')" )
> ! or diehtml("Cannot do: " . $dbh->errstr());
>
> $dbh->disconnect();
>
>
>
------------------------------
Date: Fri, 31 Aug 2001 16:14:55 +0000 (UTC)
From: Broc Seib <bseib@jade.cc.purdue.edu>
Subject: Re: Using perl for a server daemon?????
Message-Id: <9mod5v$n5v$1@mozo.cc.purdue.edu>
Gary Cub <gary@irl.com> wrote:
[snip]
> Also, if there is no reasons not to use PERL why then are more
> server daemons written in PERL??
you might check out POE: http://poe.perl.org/
and see if it is appropriate for you.
-b
------------------------------
Date: Fri, 31 Aug 2001 17:46:21 GMT
From: gauthier@circum.com (Benoit Gauthier)
Subject: Re: Weird -w behaviour
Message-Id: <3b8fcd49.29736175@news.videotron.ca>
(2001.08.31, 13:45)
>> 1) How do you figure out there were carriage returns?
>Do you think you are the first person with this problem? :-)
Touché.
Thanks very much for your help. I have located the problem and fixed
it.
Benoît Gauthier
------------------------------
Date: 31 Aug 2001 16:49:00 GMT
From: Jim Cook <jcook@strobedata.com>
Subject: Which modules have I added?
Message-Id: <3B8FBFFB.68F7428E@strobedata.com>
Well, I've gone and done something stupid.
Now that I've added several modules to my perl installation, I find that
I might want to upgrade my version of perl. Of course, I didn't keep the
original modules around, so I don't know what I should put back to keep
my existing set of scripts working.
Is there a way to tell from within perl what's been added, so I can do a
fresh download / compile / install of perl and modules?
Thanks in advance for any effort you spend on this.
--
jcook@strobedata.com Live Honourably 4/1 - 4/3 + 4/5 - 4/7 + . . .
2001 Wed: Feb/last 4/4 6/6 8/8/ 10/10 12/12 9/5 5/9 7/11 11/7 3/14
Strobe Data Inc. home page http://www.strobedata.com
My home page O- http://jcook.net
------------------------------
Date: Fri, 31 Aug 2001 17:10:15 GMT
From: "Ron Hartikka" <ronh@iainc.com>
Subject: Re: Which modules have I added?
Message-Id: <XxPj7.42426$Hm.419662@typhoon.mw.mediaone.net>
Three answers:
1) You can use ppm verify.
2) If you...
perl -c use_nonexistant_module.pl
...perl just compiles your program - won't even try to execute. If your
program contains a module not correctly installed, you get a
message:
Can't locate Notexist_here.pm in @INC (@INC contains: C:/Perl/lib
C:/Perl/site/lib .) at C:\Ron\perl\examples\use_non_existant_module.pl line
1.
BEGIN failed--compilation aborted at
C:\Ron\perl\examples\use_non_existant_module.pl line 1.
3) If you want the names of modules installed, try this:
for(@INC){
opendir DIR, $_;
print join "\n", grep /pm$/, readdir DIR;
}
...which printed...
AnyDBM_File.pm
attributes.pm
attrs.pm
AutoLoader.pm
AutoSplit.pm
autouse.pm
B.pm
base.pm
Benchmark.pm
blib.pm
ByteLoader.pm
bytes.pm
Carp.pm
CGI.pm
charnames.pm
Config.pm
constant.pm
CPAN.pm
Cwd.pm
DB.pm
diagnostics.pm
DirHandle.pm
Dumpvalue.pm
DynaLoader.pm
English.pm
Env.pm
Errno.pm
Exporter.pm
Fatal.pm
Fcntl.pm
fields.pm
FileCache.pm
FileHandle.pm
filetest.pm
FindBin.pm
integer.pm
IO.pm
less.pm
lib.pm
locale.pm
O.pm
Opcode.pm
open.pm
ops.pm
overload.pm
POSIX.pm
re.pm
Safe.pm
SDBM_File.pm
SelectSaver.pm
SelfLoader.pm
Shell.pm
sigtrap.pm
Socket.pm
strict.pm
subs.pm
Symbol.pm
Test.pm
Thread.pm
UNIVERSAL.pm
utf8.pm
vars.pm
warnings.pm
XSLoader.pmDigest.pm
LWP.pm
MD5.pm
OLE.pm
PPM.pm
SHA.pm
SOAP.pm
URI.pm
Win32.pm
Tk.pm
Storable.pm
... on this machine.
"Jim Cook" <jcook@strobedata.com> wrote in message
news:3B8FBFFB.68F7428E@strobedata.com...
> Well, I've gone and done something stupid.
>
> Now that I've added several modules to my perl installation, I find that
> I might want to upgrade my version of perl. Of course, I didn't keep the
> original modules around, so I don't know what I should put back to keep
> my existing set of scripts working.
>
> Is there a way to tell from within perl what's been added, so I can do a
> fresh download / compile / install of perl and modules?
>
> Thanks in advance for any effort you spend on this.
>
> --
> jcook@strobedata.com Live Honourably 4/1 - 4/3 + 4/5 - 4/7 + . . .
> 2001 Wed: Feb/last 4/4 6/6 8/8/ 10/10 12/12 9/5 5/9 7/11 11/7 3/14
> Strobe Data Inc. home page http://www.strobedata.com
> My home page O- http://jcook.net
------------------------------
Date: Fri, 31 Aug 2001 17:12:54 GMT
From: mjd@plover.com (Mark Jason Dominus)
Subject: Re: Which modules have I added?
Message-Id: <3b8fc596.2ba6$169@news.op.net>
In article <3B8FBFFB.68F7428E@strobedata.com>,
Jim Cook <jcook@strobedata.com> wrote:
>Is there a way to tell from within perl what's been added, so I can do a
>fresh download / compile / install of perl and modules?
1. Try 'perldoc perllocal'.
2. The CPAN module ('perldoc CPAN') may have a featur that does what
you want.
--
@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($q*=2)+=$f=!fork;map{$P=$P[$f^ord
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^[P.]/&&
close$_}%p;wait until$?;map{/^r/&&<$_>}%p;$_=$d[$q];sleep rand(2)if/\S/;print
------------------------------
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 1670
***************************************
