[23944] in Perl-Users-Digest
Perl-Users Digest, Issue: 6145 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Feb 17 06:05:48 2004
Date: Tue, 17 Feb 2004 03:05:06 -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 Tue, 17 Feb 2004 Volume: 10 Number: 6145
Today's topics:
Re: [MIME] How to attach eMails? <Guru03@despammed.com>
Re: [MIME] How to attach eMails? <tore@aursand.no>
Re: [MIME] How to attach eMails? <Guru03@despammed.com>
Re: Example of web application done right? <simonmcc@nortelnetworks.com>
List Running Applications on Win32 (!Processes) (Francis Libble)
Re: List Running Applications on Win32 (!Processes) <kalinaubears@iinet.net.au>
Re: List Running Applications on Win32 (!Processes) <kalinaubears@iinet.net.au>
MakeMaker problem <Guru03@despammed.com>
Re: more stripping <tore@aursand.no>
Re: OPEN( , Get , or slurping problem <bik.mido@tiscalinet.it>
Re: OPEN( , Get , or slurping problem <tore@aursand.no>
Re: Perl memory allocation <nospam-abuse@ilyaz.org>
Re: Perl memory allocation (Maximus)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Recommended mail module for plaintext sending? <tore@aursand.no>
Re: Regular Expresions & pattern matching (mis)understa <no@spam.for.me.invalid>
Re: Regular Expresions & pattern matching (mis)understa <usenet@morrow.me.uk>
Send an integer value through sockets in perl. (Tompyna)
Re: Send an integer value through sockets in perl. <tassilo.parseval@rwth-aachen.de>
Re: Send an integer value through sockets in perl. <usenet@morrow.me.uk>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 17 Feb 2004 08:42:54 +0000 (UTC)
From: Guru03 <Guru03@despammed.com>
Subject: Re: [MIME] How to attach eMails?
Message-Id: <Xns949262E7B1BD9Guru03despammedcom@193.43.96.1>
jwillmore@myrealbox.com (James Willmore) wrote in
news:d61170e5.0402161640.276df4f7@posting.google.com:
>> Ok, but I must return a MIME::Entity object...
>
> No, you don't - that's the beauty of using MIME::Lite - no sendmail
> required :-)
>
I'm writing a subroutine that MUST return a MIME::entity object, NOT
MIME::Lite... and it's integrated into an MTA (Postfix, qmail)...
------------------------------
Date: Tue, 17 Feb 2004 10:43:33 +0100
From: Tore Aursand <tore@aursand.no>
Subject: Re: [MIME] How to attach eMails?
Message-Id: <pan.2004.02.17.09.21.46.513576@aursand.no>
On Mon, 16 Feb 2004 10:50:26 +0000, Guru03 wrote:
> But when I open it in certain versions of Outlook the body of attached
> email is not shown, and in none of these versions I can see the headers
> (but From:, To: and Subject: yes).
It doesn't _seem_ to be anything wrong with your code, according to what I
know about MIME::Entity.
But have you tried reading the same email message in other email clients
than Outlook? I don't trust Outlook when it comes to "does it work when
sending an email like this?" stuff. :)
--
Tore Aursand <tore@aursand.no>
"Scientists are complaining that the new "Dinosaur" movie shows
dinosaurs with lemurs, who didn't evolve for another million years.
They're afraid the movie will give kids a mistaken impression. What
about the fact that the dinosaurs are singing and dancing?" -- Jay
Leno
------------------------------
Date: Tue, 17 Feb 2004 10:52:34 +0000 (UTC)
From: Guru03 <Guru03@despammed.com>
Subject: Re: [MIME] How to attach eMails?
Message-Id: <Xns949278E3C8863Guru03despammedcom@193.43.96.1>
Tore Aursand <tore@aursand.no> wrote in news:pan.2004.02.17.09.21.46.513576
@aursand.no:
> But have you tried reading the same email message in other email clients
> than Outlook? I don't trust Outlook when it comes to "does it work when
> sending an email like this?" stuff. :)
I verified that Outlook 2000 SP1 has a bug, not viewing correctly the email
attachments. 2000 (NOT SP1) and 2000 SP3 works.
------------------------------
Date: Tue, 17 Feb 2004 10:45:45 -0000
From: "Simon McCaughey" <simonmcc@nortelnetworks.com>
Subject: Re: Example of web application done right?
Message-Id: <c0sr9g$i4h$1@zcars0v6.ca.nortel.com>
<thumb_42@yahoo.com> wrote in message
news:iySXb.43206$_44.39503@attbi_s52...
<snip>
> As far as the web front.. I would really not recommend perl for this
What would you recommend? and what did you use?
> portion. (at this time) But, if you're going to do it, keep it a very
simple
> model-view-controller, and use a templating system that makes sense for
your
> needs. Be very wary of any session handling, as soon as you need session
> data you'll have a mess in keeping synchronized sessions across multiple
web
> hosts. (session handling was by far the biggest issue we had with this
> thing)
Did you manage without session data? or how did you handle this problem?
Simon
------------------------------
Date: 17 Feb 2004 02:07:30 -0800
From: garyoffsite@yahoo.co.uk (Francis Libble)
Subject: List Running Applications on Win32 (!Processes)
Message-Id: <955f45df.0402170207.2cc86c3b@posting.google.com>
Dear All
Can someone tell me how to get a list of running applications on
Win32?
I am essentially looking to get the same list as appears in the
Applications tab of the Windows Task Manager. I can easily get the
equivalent of the Processes tab in Windows Task Manager (using
Win32::Setupsup or Win32::IProc) but I can't seem to find a way to
retrieve only the running applications.
Enumerating Window titles doesn't give me what I am looking for either
(hidden windows with titles show up)
Thanks
Flibble
------------------------------
Date: Tue, 17 Feb 2004 21:15:39 +1100
From: Sisyphus <kalinaubears@iinet.net.au>
Subject: Re: List Running Applications on Win32 (!Processes)
Message-Id: <4031eacb$0$22512$5a62ac22@freenews.iinet.net.au>
Francis Libble wrote:
> Dear All
>
> Can someone tell me how to get a list of running applications on
> Win32?
> I am essentially looking to get the same list as appears in the
> Applications tab of the Windows Task Manager. I can easily get the
> equivalent of the Processes tab in Windows Task Manager (using
> Win32::Setupsup or Win32::IProc) but I can't seem to find a way to
> retrieve only the running applications.
>
> Enumerating Window titles doesn't give me what I am looking for either
> (hidden windows with titles show up)
>
Win32::PerfLib (part of libwin) or Win32::Process::Info (my preference).
Cheers,
Rob
--
To reply by email u have to take out the u in kalinaubears.
------------------------------
Date: Tue, 17 Feb 2004 21:45:19 +1100
From: Sisyphus <kalinaubears@iinet.net.au>
Subject: Re: List Running Applications on Win32 (!Processes)
Message-Id: <4031f1be$0$22532$5a62ac22@freenews.iinet.net.au>
Sisyphus wrote:
>
> Win32::PerfLib (part of libwin) or Win32::Process::Info (my preference).
>
Oops - now that I read your post properly I'm not sure that either of
those modules supply what you want. Check them out, anyway :-)
Cheers,
Rob
--
To reply by email u have to take out the u in kalinaubears.
------------------------------
Date: Tue, 17 Feb 2004 10:54:53 +0000 (UTC)
From: Guru03 <Guru03@despammed.com>
Subject: MakeMaker problem
Message-Id: <Xns94927947F453Guru03despammedcom@193.43.96.1>
Hi, I want to put my executables of EXE_FILES into /usr/sbin with:
INSTALLSITEDIR => '/usr/sbin'
but the MakeMaker tells me:
'INSTALLSITEBIN' is not a known MakeMaker parameter name.
That word is reported on the CPAN site. This happens in both 5.50 and
latest version.
------------------------------
Date: Tue, 17 Feb 2004 10:43:32 +0100
From: Tore Aursand <tore@aursand.no>
Subject: Re: more stripping
Message-Id: <pan.2004.02.17.09.39.44.123629@aursand.no>
On Mon, 16 Feb 2004 14:12:01 -0600, Michael Hill wrote:
> Subject: more stripping
Could have been an excellent Subject. :)
> The input looks like:
>
> <path fill="none" stroke="#000000" d="M0.437,185.49l87-156"/>
> <path fill="none" stroke="#000000" d="M87.437,29.49l140-29"/>
> <path fill="none" stroke="#000000" d="M227.437,0.49l39,118"/>
> <path fill="none" stroke="#000000" d="M266.437,118.49l-104,160"/>
> <path fill="none" stroke="#000000" d="M159.437,276.49l-32-101"/>
> <path fill="none" stroke="#000000" d="M127.437,175.49l-127,10"/>
Really? Where do you get this input from?
> This is where I am:
> ****************************************************************
> read(STDIN, $buffer, $ENV{'CONTENT_LENGTH'});
> @pairs = split(/&/, $buffer);
> foreach $pair (@pairs)
> {
> ($name, $value) = split(/=/, $pair);
> $value =~ s/%09//g; #strip the tabs out all of them
> $value =~ s/%3C//g; #strip the < all of them
> $value =~ s/%2F%3E//g; #strip the /> all of them
> $value =~ s/%22//g; #strip the " all of them
> $value =~ s/%23//g; #strip the # all of them
> $value =~ s/%3D/=/g; #change %3D to = all of them
> $value =~ s/%2C/,/g; #change %2C to , all of them
> $value =~ s/%0D%0A//g; #strip out the carriage returns
> $value =~ s/path//g; #strip out the word path .....
> hmmm what if i have 'PATH' or Path or paTH? Need mod here
> if ( $name eq 'path' )
> {
> $path = $value;
> }
> }
>
> @arr = split(/+/, $path);
> foreach $i (@arr)
> {
> ($x, $y) = @$i;
> print "d=$x,$y<br>";
> }
Don't you _ever_ - and I really mean _ever_ - try to hand-roll this on
your own. Let CGI.pm do that for you (untested):
#!/usr/bin/perl
#
use strict;
use warnings;
use CGI;
my $CGI = CGI->new();
my $params = $CGI->Vars();
foreach ( keys %$params ) {
print $_ . ' = ' . $params->{$_} . "\n";
}
I never use the Vars() function, though, as I tend to always know what I'm
looking for in the CGI request.
--
Tore Aursand <tore@aursand.no>
"Writing is a lot like sex. At first you do it because you like it.
Then you find yourself doing it for a few close friends and people you
like. But if you're any good at all, you end up doing it for money."
-- Unknown
------------------------------
Date: Tue, 17 Feb 2004 08:54:54 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: OPEN( , Get , or slurping problem
Message-Id: <06h330tppg0ksl4rpkn3f9pflvb5agqkon@4ax.com>
On Mon, 16 Feb 2004 21:59:48 +0100, Gunnar Hjalmarsson
<noreply@gunnar.cc> wrote:
> use LWP::Simple;
> my $site = get 'http://www.webbuyeruk.co.uk/links.htm';
> while ( $site =~ /(.*)/g ) {
> if ($1 =~ /PATTERN/) {
> print "Found\n";
> last;
> }
> }
[...]
>> open(MYFILE, "<($site[0])") || die "Can't open $site[0] : $!\n";;
>
>You can't open a URL! Please learn the difference between a path and a
>URL.
But then, if he *really* wants to open() the downloaded HTML, he could
do that "in memory":
# untested
open my $file, '<', \$site or die $!;
do_something while <$file>;
Michele
--
#!/usr/bin/perl -lp
BEGIN{*ARGV=do{open $_,q,<,,\$/;$_}}s z^z seek DATA,11,$[;($,
=ucfirst<DATA>)=~s x .*x q^~ZEX69l^^q,^2$;][@,xe.$, zex,s e1e
q 1~BEER XX1^q~4761rA67thb ~eex ,s aba m,P..,,substr$&,$.,age
__END__
------------------------------
Date: Tue, 17 Feb 2004 10:43:31 +0100
From: Tore Aursand <tore@aursand.no>
Subject: Re: OPEN( , Get , or slurping problem
Message-Id: <pan.2004.02.17.09.32.14.147367@aursand.no>
On Mon, 16 Feb 2004 12:04:27 -0800, Chris wrote:
> #!/usr/local/bin/perl -w
> use warnings;
> use strict;
No need for the '-w' flag as long as you 'use warnings';
#!/usr/local/bin/perl
#
use strict;
use warnings;
> use LWP::Simple;
> my @site = ("http://www.webbuyeruk.co.uk/links.htm");
>
> foreach my $site (@site){
> my @content = get ($site);
>
> print "Array entries: $#content\n";
> }
>
> the above puts all of the lines into the first array entry [0], how
> can I change this??
You usually don't want to change this, unless you really have to.
LWP::Simple's get() function returns a string. You could always split the
string on line breaks, but do you really have to?
foreach ( @site ) {
my $content = get( $_ );
unless ( defined $content ) {
# Error
}
}
> open(MYFILE, "<($site[0])") || die "Can't open $site[0] : $!\n";;
> my @filedata = <MYFILE>;
> close(MYFILE);
$site[0] refers to the first element of @site, which is the URL of the
site (mentioned in your code).
If you told us what you want to do with the returning HTML, we could
probably give you some tips to some modules which would help you out.
--
Tore Aursand <tore@aursand.no>
"Leadership is doing what is right when no one is watching." -- George
Van Valkenburg
------------------------------
Date: Tue, 17 Feb 2004 10:17:51 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Perl memory allocation
Message-Id: <c0spof$kkd$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
Ben Morrow
<usenet@morrow.me.uk>], who wrote in article <c0r7dr$kul$2@wisteria.csv.warwick.ac.uk>:
> > > My Perl is compiled with the OS's malloc rather than Perls.
> >
> > How is that relevant?
>
> perlfaq3.pod:
> | Some operating systems [...] can reclaim memory that is no longer
> | used, but on such systems, perl must be configured and compiled to use
> | the OS's malloc, not perl's.
>
> was no doubt confusing the OP... the important part is 'Some OSen'.
> Clearly the OP's isn't one of them.
Well, given that the FAQ entry is wrong, it is not the only reason for
confusion... The correct answer should be something like "some OSes
in some situations"...
> (As an aside, would it be feasible to change perl's malloc to use mmap
> where possible, and release mem back to the OS? This seems to be quite
> often wanted...)
Do not think that this is often *wanted*; but anyway, a lot of people
may *think* they want this. ;-)
BTW, such a change is in my TODO list for many years; but given that I
can't work on Perl without grants any more, it does not have a large
chance to float to the front of my list...
Hope this helps,
Ilya
------------------------------
Date: 17 Feb 2004 02:57:33 -0800
From: anio@webgroup-bg.com (Maximus)
Subject: Re: Perl memory allocation
Message-Id: <d28ce48d.0402170257.7b5d6bc1@posting.google.com>
>
> My variable is a global, so it will never go out of scope, but I've tried
> "$var = undef;" without any success.
$var = undef; ??? What is this?
undef $var; That is!!! :)))
------------------------------
Date: Tue, 17 Feb 2004 02:22:23 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <jrmdne4_5oWiUqzdRVn_iw@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.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://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
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 17 Feb 2004 10:43:32 +0100
From: Tore Aursand <tore@aursand.no>
Subject: Re: Recommended mail module for plaintext sending?
Message-Id: <pan.2004.02.17.09.25.03.283233@aursand.no>
On Mon, 16 Feb 2004 14:21:22 +0000, Ian.H wrote:
> There are many mail modules on CPAN.. but are any recommended over
> others for sending mails? This only needs to be simple and send
> plaintext mails only. The lighter the module the better.
I prefer MIME::Lite when sending emails, but it isn't as light-weight as
the Net::SMTP module. The latter is also included in the Perl
distribution (at least for my Perl 5.8.2 installation).
--
Tore Aursand <tore@aursand.no>
"The purpose of all war is ultimately peace." -- Saint Augustine
------------------------------
Date: Tue, 17 Feb 2004 08:10:34 GMT
From: Nils Petter Vaskinn <no@spam.for.me.invalid>
Subject: Re: Regular Expresions & pattern matching (mis)understanding
Message-Id: <pan.2004.02.17.08.07.16.27997@spam.for.me.invalid>
On Mon, 16 Feb 2004 08:38:27 -0600, Tad McClellan wrote:
> Nils Petter Vaskinn <no@spam.for.me.invalid> wrote:
>
>> and probably wrong
>
>> /^(.*)<page>([0-9]+)</page>(.*)/;
>> $page = $2;
>> $rest = $1 . $3;
>
>
> Using the dollar-digit variables without first ensuring that
> the match succeeded is indeed wrong.
And i should probably have escaped that '/'
if ( /^(.*)<page>([0-9]+)<\/page>(.*)/ ) {
$page = $2;
$rest = $1 . $3;
}
--
NPV
"the large print giveth, and the small print taketh away"
Tom Waits - Step right up
------------------------------
Date: Tue, 17 Feb 2004 09:28:54 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Regular Expresions & pattern matching (mis)understanding
Message-Id: <c0smsm$l5o$2@wisteria.csv.warwick.ac.uk>
Nils Petter Vaskinn <no@spam.for.me.invalid> wrote:
>
> And i should probably have escaped that '/'
>
> if ( /^(.*)<page>([0-9]+)<\/page>(.*)/ ) {
Bleech!
if ( m|^(.*)<page>(\d+)</page>(.*)| ) {
Ben
--
Musica Dei donum optimi, trahit homines, trahit deos. |
Musica truces molit animos, tristesque mentes erigit. | ben@morrow.me.uk
Musica vel ipsas arbores et horridas movet feras. |
------------------------------
Date: 16 Feb 2004 22:04:27 -0800
From: thomaspoly@mail.com (Tompyna)
Subject: Send an integer value through sockets in perl.
Message-Id: <9af8a23a.0402162204.200fa56f@posting.google.com>
Hi All,
I am very much new to socket programming in perl. I had written
a small socket client and server program to send and receive a string
value.
my $msg = "hello";
send(SOCKET,$msg,10,MSG_OOB ) ----- > will send the string "hello".
With the above code i was able to send an string value, and receive
the value in the client.Now my starts here.... .
But if i need to send an integer. i tried sending by giving
my $msg = 10;
$Returned_val = send(SOCKET,$msg,4,MSG_OOB );
print "\nNo: of characters send '",$Returnned_val,"'";
This will take 10 as string value and send it.
Because the printed Returned_val == 2 , and not 4 .
Can anyone suggest any way to send an integer value through sockets in
perl?.
Thanx.... in advance.
Thomas Poly.
------------------------------
Date: 17 Feb 2004 07:07:59 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Send an integer value through sockets in perl.
Message-Id: <c0sekf$peu$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Tompyna:
> I am very much new to socket programming in perl. I had written
> a small socket client and server program to send and receive a string
> value.
> my $msg = "hello";
> send(SOCKET,$msg,10,MSG_OOB ) ----- > will send the string "hello".
>
> With the above code i was able to send an string value, and receive
> the value in the client.Now my starts here.... .
>
> But if i need to send an integer. i tried sending by giving
>
> my $msg = 10;
>
> $Returned_val = send(SOCKET,$msg,4,MSG_OOB );
>
> print "\nNo: of characters send '",$Returnned_val,"'";
>
> This will take 10 as string value and send it.
> Because the printed Returned_val == 2 , and not 4 .
So you don't actually want to send the string "10" but rather 10 as a
32bit integer? In this case you have to pack it. You can choose between
two byteorders. Network byteorder (bigendian) seems appropriate here:
my $msg = pack "N", 10;
my $ret = send(SOCKET, $msg, 4, MSG_OOB);
The receiver then just has to unpack it again:
my $num = unpack "N", $received;
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: Tue, 17 Feb 2004 09:27:16 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Send an integer value through sockets in perl.
Message-Id: <c0smpk$l5o$1@wisteria.csv.warwick.ac.uk>
thomaspoly@mail.com (Tompyna) wrote:
> Hi All,
> I am very much new to socket programming in perl. I had written
> a small socket client and server program to send and receive a string
> value.
> my $msg = "hello";
> send(SOCKET,$msg,10,MSG_OOB ) ----- > will send the string "hello".
Are you sure you want to send the value as out-of-band data? Do you not
just want to send it normally:
my $msg = pack 'a10', 'hello'; # null-padded, use A10 for space-padded
print SOCKET $msg;
Also, you may find life easier if you use the IO::Socket modules.
Ben
--
If you put all the prophets, | You'd have so much more reason
Mystics and saints | Than ever was born
In one room together, | Out of all of the conflicts of time.
ben@morrow.me.uk |----------------+---------------| The Levellers, 'Believers'
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 6145
***************************************
