[23554] in Perl-Users-Digest
Perl-Users Digest, Issue: 5762 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Nov 7 06:05:48 2003
Date: Fri, 7 Nov 2003 03:05:07 -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 Fri, 7 Nov 2003 Volume: 10 Number: 5762
Today's topics:
Re: Accessing PHP variables with Perl <jwillmore@remove.adelphia.net>
Breaking out of loop if nothing pending <neil.shadrach@corryn.com>
Re: Breaking out of loop if nothing pending <ak+usenet@freeshell.org>
Re: Breaking out of loop if nothing pending (Anno Siegel)
Re: Breaking out of loop if nothing pending <spamfilter@cheiron-it.nl>
Re: Code to generate random file names <mb@uq.net.au>
count of 1s in a binary number <fJogham@yahoo.com>
Re: count of 1s in a binary number (Sam Holden)
Re: count of 1s in a binary number <tassilo.parseval@rwth-aachen.de>
Re: count of 1s in a binary number <pinyaj@rpi.edu>
Re: how to access a (global) variable across files (Newbie)
Re: Newbie gets Internal Server Error, among others (Anno Siegel)
Perl features <moliverius@w-link.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Speech recognition! <someone@somewhere.com>
Re: Tool to embed images (or other binaries) in your P <ssNO@SPAMaao.gov.au>
Re: Tool to embed images (or other binaries) in your P <usenet@giantsquidmarks.com>
Re: wolk a byte code tree <pavel@gingerall.cz>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 07 Nov 2003 05:08:23 GMT
From: James Willmore <jwillmore@remove.adelphia.net>
Subject: Re: Accessing PHP variables with Perl
Message-Id: <20031107000809.420779f1.jwillmore@remove.adelphia.net>
On Fri, 07 Nov 2003 03:12:06 GMT
"Kubaton Lover" <spamsucks@noemail.com> wrote:
> I have a site which is primarily PHP and I'm setting a bunch of PHP
> environment variables with statements like:
> $HTTP_SESSION_VARS['valid_user'] = $userid;
>
> Is there a way for my Perl scripts to access those session
> variables? I've never done that before with Perl.
Try using the PHP::Session module
http://search.cpan.org/~miyagawa/PHP-Session-0.22/lib/PHP/Session.pm
HTH
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
Death is God's way of telling you not to be such a wise guy.
------------------------------
Date: Fri, 7 Nov 2003 10:14:46 +0000 (UTC)
From: Neil Shadrach <neil.shadrach@corryn.com>
Subject: Breaking out of loop if nothing pending
Message-Id: <bofram$j2$3@visp.bt.co.uk>
# perl -we 'die q(KO) unless open(my $h,q(tail -f logfile1.txt|));while (<$h>) { print "L:$_"; }'
Can I easily break out of the 'while' loop if nothing is there to be read
or do I need to use a lower level read function to be able to do this?
------------------------------
Date: Fri, 7 Nov 2003 10:26:16 +0000 (UTC)
From: Andreas Kahari <ak+usenet@freeshell.org>
Subject: Re: Breaking out of loop if nothing pending
Message-Id: <slrnbqmsq6.g7r.ak+usenet@vinland.freeshell.org>
In article <bofram$j2$3@visp.bt.co.uk>, Neil Shadrach wrote:
> # perl -we 'die q(KO) unless open(my $h,q(tail -f logfile1.txt|));while (<$h>) { print "L:$_"; }'
>
> Can I easily break out of the 'while' loop if nothing is there to be read
> or do I need to use a lower level read function to be able to do this?
The way "tail -f" works is that it will wait for input until
killed. So what are your criteria for "nothing to be read"?
--
Andreas Kähäri
------------------------------
Date: 7 Nov 2003 10:35:49 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Breaking out of loop if nothing pending
Message-Id: <bofsi5$g95$1@mamenchi.zrz.TU-Berlin.DE>
Neil Shadrach <neil.shadrach@corryn.com> wrote in comp.lang.perl.misc:
> # perl -we 'die q(KO) unless open(my $h,q(tail -f logfile1.txt|));while
> (<$h>) { print "L:$_"; }'
>
> Can I easily break out of the 'while' loop if nothing is there to be read
> or do I need to use a lower level read function to be able to do this?
I don't know what you mean by "nothing to read". The job of "tail -f"
is to wait until there *is* something to read, so most of the time there
will be nothing to read.
If you want to modify the behavior of "tail -f", see the _Perl Cookbook_.
It has one or more recipes to emulate "tail -f" in Perl, so that would
be a good starting point.
Anno
------------------------------
Date: Fri, 7 Nov 2003 11:35:32 +0100
From: "Frank Maas" <spamfilter@cheiron-it.nl>
Subject: Re: Breaking out of loop if nothing pending
Message-Id: <3fab7574$0$149$e4fe514c@dreader7.news.xs4all.nl>
"Neil Shadrach" :
> # perl -we 'die q(KO) unless open(my $h,q(tail -f logfile1.txt|));while
(<$h>) { print "L:$_"; }'
>
> Can I easily break out of the 'while' loop if nothing is there to be read
> or do I need to use a lower level read function to be able to do this?
'tail -f' means 'show me the tail of the file and keep on showing me
additions to the file'. Seems to me that in this context there is no such
thing as 'nothing there to read'. Could you elaborate on your needs?
--Frank
------------------------------
Date: Fri, 07 Nov 2003 17:06:21 +1000
From: Matthew Braid <mb@uq.net.au>
Subject: Re: Code to generate random file names
Message-Id: <bofg9c$5f6$1@bunyip.cc.uq.edu.au>
Kev wrote:
> I'm downloading files from the internet and need some code that would use
> the time to name the files. Could someone who may have this code share it?
>
> Thanks.
>
> Kev
>
>
If you absolutely must have the time in there somewhere, you can do
something like: (UNTESTED!)
----- START CODE -----
use Fcntl qw/O_WRONLY O_CREAT O_EXCL/;
use IO::File;
my $dir = '/tmp/'; # Or wherever
my $perms = 0640; # You may want to change this
my @time = localtime;
$time[4]++;
$time[5] += 1900;
my $fh = IO::File->new;
my $fname;
while (1) {
my $rnd = int(rand(1e14)); # sprintf can't handle %014d
$rnd = ('0' x (14 - length($rnd))) . $rnd;
$fname = sprintf("$dir%04d%02d%02d%02d%02d%02d.$rnd",
reverse(@time[0..5]));
last if $fh->open($fname, O_CREAT|O_EXCL|O_WRONLY, $perms);
next if $! =~ /File exists/;
die "Failed to create file - $!";
}
print "Created a new file named $fname\n";
$fh->close; # Obviously you'd do something with $fh first
----- END CODE -----
This would give you a filename (and an open filehandle, which is even
more useful) of something like /tmp/20031107165921.00197626901823.
All it expects is that you already know where the temp directory is but
I'm guessing there's a handy package out there for giving you that too.
MB
------------------------------
Date: Fri, 07 Nov 2003 18:36:24 +1100
From: Fred <fJogham@yahoo.com>
Subject: count of 1s in a binary number
Message-Id: <3FAB4B78.4030400@yahoo.com>
if there is not a function that takes a scalar or array and count a
given charcter. I am trying to come up with a code
the main issue is how to get the sub to deal with both data types and
give the expected results which is the count of "1" in the string or
array with out writeing 2 subs
my $bit1 = "011001010";
my @bit2 = qw /01 00 11 01 00/;
print size_of($bit1), "\n";
print size_of(@bit2), "\n";
sub size_of {
my $tmp = shift;
my $i = 0;
foreach my $j (split //, $tmp) {
if ( $j == 1 ) { $i++ };
}
return $i;
}
thanks
------------------------------
Date: 7 Nov 2003 06:38:24 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: count of 1s in a binary number
Message-Id: <slrnbqmff0.q6u.sholden@flexal.cs.usyd.edu.au>
On Fri, 07 Nov 2003 17:29:16 +1100, Fred <fJogham@yahoo.com> wrote:
> if there is not a function that takes a scalar or array and count a
> given charcter. I am trying to come up with a code
perldoc -q count
How can I count the number of occurrences of a substring within a string?
The idea is to readand FAQ before asking questions.
--
Sam Holden
------------------------------
Date: 7 Nov 2003 07:08:44 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: count of 1s in a binary number
Message-Id: <bofgds$phe$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Fred:
> if there is not a function that takes a scalar or array and count a
> given charcter. I am trying to come up with a code
>
>
> my $bit1 = 011001010;
> my @bit2 = qw /01 00 11 01 00/;
> print size ($bit1) "\n";
> print size (@bit2) "\n";
>
> I need a function which works on both data types
No need for a for-loop here:
sub size {
return "@_" =~ tr/1//;
}
> sub size {
> my $tmp = shift;
> my $i = 0;
> foreach my $j ( @tmp ) {
> if ( $j == 1 ) { $i++ };
> }
> return $i;
> }
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Fri, 7 Nov 2003 03:05:04 -0500
From: Jeff 'japhy' Pinyan <pinyaj@rpi.edu>
Subject: Re: count of 1s in a binary number
Message-Id: <Pine.SGI.3.96.1031107030357.69815A-100000@vcmr-64.server.rpi.edu>
On 7 Nov 2003, Tassilo v. Parseval wrote:
>No need for a for-loop here:
>
> sub size {
> return "@_" =~ tr/1//;
> }
Pedantic mode on:
sub size {
join("", @_) =~ tr/1//;
}
or
sub size {
local $" = "";
"@_" =~ tr/1//;
}
--
Jeff Pinyan RPI Acacia Brother #734 2003 Rush Chairman
"And I vos head of Gestapo for ten | Michael Palin (as Heinrich Bimmler)
years. Ah! Five years! Nein! No! | in: The North Minehead Bye-Election
Oh. Was NOT head of Gestapo AT ALL!" | (Monty Python's Flying Circus)
------------------------------
Date: 7 Nov 2003 00:44:37 -0800
From: diwaneel@yahoo.com (Newbie)
Subject: Re: how to access a (global) variable across files
Message-Id: <8a54fd80.0311070044.176cd265@posting.google.com>
thanks 4 ur replies... but thats not working... something trivial is
going wrong somewhere
i m doing it from scratch. m creating 2 files A.pl:
#!/user/local/bin/perl
use strict;
use B;
my $varA = "cfgA";
$B::varG = "cfgG";
print "Inside PL file....varA = $varA\n";
print "Inside PL file....varG = $B::varG\n";
&B::test ();
and B.pm:
package B;
local $varG;
@EXPORT = qw (&test $varG);
sub test () {
print "a: $main::varA\n";
print "varG = $varG\n";
}
1;
running A.pl, it gives:
Undefined subroutine &B::test called at A.pl line 12.
P.S.: I have set the env var PERL5LIB=mydir
Please reply
------------------------------
Date: 7 Nov 2003 10:03:47 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Newbie gets Internal Server Error, among others
Message-Id: <bofqm3$f4b$1@mamenchi.zrz.TU-Berlin.DE>
Jessica Smith <jessis@cobweb.net> wrote in comp.lang.perl.misc:
> I'm using Mac OS X, and I'm trying to run a script I copied from a
> tutorial. The script is online at
> http://www.elanus.net/cgi/examples.cgi/view/ex_0302.txt
>
> It's chmod'ed 755, just like it should be, and the sh-bang line is
> correct. Yet, when I run the program in Terminal, I get:
How do you run it? Show the exact call.
> ./mail_form.cgi: =: command not found
This message (and the following ones) say that you tried to run the
script as an sh script. In the configuration statements, beginning
with "$sendmail = '/usr/sbin/sendmail'; # where is sendmail?", sh
tries to run "=" as a command, that's why it complains five times.
And so on.
If you didn't explicitly call it as "sh mail_form.cgi", that means the
shebang line isn't recognized by your system.
Anno
------------------------------
Date: Fri, 07 Nov 2003 01:37:17 -0500
From: Matt Oliverius <moliverius@w-link.net>
Subject: Perl features
Message-Id: <vqmoj11cc8n5a1@corp.supernews.com>
I am a huge Perl fan. However, after spending the last 4 years of my
career learning and developing Perl skills, my company is trying to ax
Perl. In a nutshell, the people that are supposed to be our company
experts, posted a bunch of false crap on a website that stated such false
statements as:
1) Perl is hard to understand and maintain (oh yeah, great reason to
abandon a language, do we then abandon see because we have to worry about
low level memory management?)
2) Perl is not object-oriented
I, along with about 100 others, flamed the heck out of this guy (who is a
supposed Associate Technical Fellow).
Anyway, he is giving bean-counter managers the impression that Python is
light years ahead of Perl and that Python should be used over Perl for any
new applications. Does any know of any major shortcomings of Python that
Perl can handle? I really want to beat on this guy a little.
------------------------------
Date: Fri, 07 Nov 2003 02:22:17 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <rLWdnWTq0fmkyzaiRVn-hg@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.4 $)
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":
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
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 7 Nov 2003 09:13:09 -0000
From: "Bigus" <someone@somewhere.com>
Subject: Re: Speech recognition!
Message-Id: <bofnn6$q8m@newton.cc.rl.ac.uk>
"Anno Siegel" <anno4000@lublin.zrz.tu-berlin.de> wrote in message
news:bodcss$o8a$4@mamenchi.zrz.TU-Berlin.DE...
> Bigus <someone@somewhere.com> wrote in comp.lang.perl.misc:
> > Perhaps partly OT here, but does anyone know of good (and pref. free)
speech
> > recognition software, that can output a text string that could be read
and
> > acted upon by a Perl script?
>
> Search the CPAN for "speech". There are a few hits.
It never ceases to amaze me the diversity of modules you get on there.. I
was thinking I would probably (finally) have to attempt to learn C to do my
latest project, but it seems Perl may well be able to handle all the tasks I
will need to give it!
> > For that matter, can Perl be made TSR so
that
> > it sits and "listens" for input, such as text from a speech recog
software?
>
> TSR (terminate and stay resident) appears to be a DOS technique to hold
> programs in memory. Perl is a programming language, TSR doesn't apply.
>
> If the question is whether a Perl program can be made TSR, I don't know.
> You can certainly keep a Perl program running in the background, waiting
> for input from some other program. See "perldoc perlipc" for that.
Ouch.. that looks complicated.. but thanks :)
Bigus
------------------------------
Date: Fri, 07 Nov 2003 05:06:16 GMT
From: "Scott Smedley" <ssNO@SPAMaao.gov.au>
Subject: Re: Tool to embed images (or other binaries) in your Perl source.
Message-Id: <pan.2003.11.07.05.05.03.559030@SPAMaao.gov.au>
> I performed a search-replace
You need to fix this line:
#!/usr/bin/Perl -w
SCoTT. :)
------------------------------
Date: Thu, 6 Nov 2003 23:36:55 -0700
From: "Michael Carey" <usenet@giantsquidmarks.com>
Subject: Re: Tool to embed images (or other binaries) in your Perl source.
Message-Id: <3fab3d74_1@127.0.0.1>
halarious...! fixed...
----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
------------------------------
Date: Fri, 07 Nov 2003 09:38:58 +0100
From: Pavel Hlavnicka <pavel@gingerall.cz>
To: Dave Roe <davidroe@email.com>
Subject: Re: wolk a byte code tree
Message-Id: <3FAB5A22.2080602@gingerall.cz>
Thank you very much, the Safe module seems to be quite sufficient. Sorry
for my ignorance :)
Pavel
Dave Roe wrote:
> as someone else suggested, the Safe module might be what you are after.
> otherwise, is it something you could interrogate first with something
> like Parse::RecDescent?
>
> /dave
>
> Pavel Hlavnicka wrote:
>
>> Hi all,
>>
>> this is a bit advanced question. I'm developing and application which
>> is a finite state automaton, where actions to be take on particular
>> state are described in an external configuration files as a Perl
>> expressions.
>>
>> To keep the code as safe as possible, I want to allow only particular
>> function names and variable names might be used in such external
>> expressions and run a Perl interpreter in a taint mode.
>>
>> What I need is to pre-check the expression to be evaluated. Regular
>> expression could become quite complex for this stuff, while walking
>> the byte code tree seems to be a simple recursive algorithm.
>>
>> Problem is, that I have no clue where to start and I'm to lazy :) and
>> under such a time pressure that I need your help. {Please give me some
>> tips, where to start and how to walk a instruction tree. All I need is
>> to quit if non-desired tree item is met. I think 'B' module family is
>> the solution.
>>
>> Thank you VERY much in advance.
>>
>> Pavel
>>
>
--
Pavel Hlavnicka
Ginger Alliance
www.gingerall.com
------------------------------
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 5762
***************************************
