[29200] in Perl-Users-Digest
Perl-Users Digest, Issue: 444 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri May 18 06:10:22 2007
Date: Fri, 18 May 2007 03:09:05 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 18 May 2007 Volume: 11 Number: 444
Today's topics:
[newbie] Year in two digits; Time with leading zero <nospam@nospam.com>
Re: [newbie] Year in two digits; Time with leading zero <ts@dionic.net>
Re: [newbie] Year in two digits; Time with leading zero <rvtol+news@isolution.nl>
Re: Apache+Perl Net::SMTP Strange problem zhaoningli@gmail.com
Calling alarm more than once iulukus@gmail.com
Re: Calling alarm more than once <ts@dionic.net>
Re: encoding problem on Tk entry widget <filippo2991@virgilio.it>
Lindsay Lohans TITS! OOPSIE! britneysspears1@gmail.com
new CPAN modules on Fri May 18 2007 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Setting up YaBB Perl forum - weird respond as plain <bik.mido@tiscalinet.it>
Support you the best free forum! <forumgogo@gmail.com>
Re: Year in two digits; Time with leading zero <jue@monster-berlin.de>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 18 May 2007 10:10:43 +0200
From: Gilles Ganault <nospam@nospam.com>
Subject: [newbie] Year in two digits; Time with leading zero
Message-Id: <0mnq431eosb3upimj6g4g7jht6tp752ccs@4ax.com>
Hello
As indicated in the subject line, I don't Perl, but I must
write a short script in it.
I just need to get the current year in two digits, and time should be
HH:MM with leading zeros if needed, ie. 10:01 instead of 10:1.
Here's what I found:
------------------------------
($min, $hrs, $day, $month, $year) = (localtime) [1,2,3,4,5];
#BAD : 2007
$currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year+1900);
#BAD : 107!
$currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year);
print $currentdate . "\n";
#BAD : 10:1 instead of 10:01
$currenttime = sprintf("%d:%d", $hrs,$min);
print $currenttime . "\n";
------------------------------
Should I use an other library?
Thank you.
------------------------------
Date: Fri, 18 May 2007 10:11:18 +0100
From: Tim Southerwood <ts@dionic.net>
Subject: Re: [newbie] Year in two digits; Time with leading zero
Message-Id: <464d6db6$0$648$5a6aecb4@news.aaisp.net.uk>
Gilles Ganault wrote:
> Hello
>
> As indicated in the subject line, I don't Perl, but I must
> write a short script in it.
>
> I just need to get the current year in two digits, and time should be
> HH:MM with leading zeros if needed, ie. 10:01 instead of 10:1.
>
> Here's what I found:
>
> ------------------------------
> ($min, $hrs, $day, $month, $year) = (localtime) [1,2,3,4,5];
>
> #BAD : 2007
> $currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year+1900);
> #BAD : 107!
> $currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year);
> print $currentdate . "\n";
>
> #BAD : 10:1 instead of 10:01
> $currenttime = sprintf("%d:%d", $hrs,$min);
> print $currenttime . "\n";
> ------------------------------
>
> Should I use an other library?
>
> Thank you.
You could "use POSIX" and make use of the standard strftime() function
assuming you are on a POSIX compliant system where that works.
But there's nothing wrong with your method either - I'd use either with no
sense that one is better or worse than the other. Your method is definately
portable, which I seldom care about because I work with nothing but *nix,
but I'm an old grumbleweed and portability is good...Honest :)
Cheers
Tim
------------------------------
Date: Fri, 18 May 2007 11:18:45 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: [newbie] Year in two digits; Time with leading zero
Message-Id: <f2k2b7.pc.1@news.isolution.nl>
Gilles Ganault schreef:
> As indicated in the subject line, I don't Perl, but I must
> write a short script in it.
>
> I just need to get the current year in two digits, and time should be
> HH:MM with leading zeros if needed, ie. 10:01 instead of 10:1.
>
> Here's what I found:
>
> ------------------------------
> ($min, $hrs, $day, $month, $year) = (localtime) [1,2,3,4,5];
>
> #BAD : 2007
> $currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year+1900);
> #BAD : 107!
> $currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year);
> print $currentdate . "\n";
How about "$year % 100"?
> #BAD : 10:1 instead of 10:01
> $currenttime = sprintf("%d:%d", $hrs,$min);
> print $currenttime . "\n";
You forgot the "02" parts:
$currenttime = sprintf("%02d:%02d", $hrs, $min);
#!/usr/bin/perl
use strict;
use warnings;
my ($min, $hrs, $day, $month, $year) = (localtime)[1..5];
my $currentdate = sprintf( "%02d/%02d/%02d",
$day,
$month + 1,
$year % 100,
);
print "$currentdate\n";
my $currenttime = sprintf( "%02d:%02d",
$hrs,
$min,
);
print "$currenttime\n";
__END__
Consider the ISO 8601 date format:
http://en.wikipedia.org/wiki/ISO_8601
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 17 May 2007 20:38:54 -0700
From: zhaoningli@gmail.com
Subject: Re: Apache+Perl Net::SMTP Strange problem
Message-Id: <1179459534.258208.101760@h2g2000hsg.googlegroups.com>
Problem has been resolved. Because I enabled SELiunx in FC5, if I
setenforce to 0, there will be no problem.
On May 18, 3:04 am, "J. Gleixner" <glex_no-s...@qwest-spam-no.invalid>
wrote:
> zhaonin...@gmail.com wrote:
> > On May 16, 2:07 pm, zhaonin...@gmail.com wrote:
> >> I am setting up a web application using apache 2.2 + perl v5.8.8 on
> >> FC5. The application needs to send out email using a SMTP server as
> >> mail relay (MTA). I wrote a test perl script test.cgi. Run the script
> >> as CGI, it always return with errors. The code fails at:
>
> >> my $smtp=new Net::SMTP($smtpserver, Timeout =>60) || die 'Cannot
> >> connect to smtp server';
>
> >> The apache server is configured to run at apache:apache. The above
> >> script works well if I use
>
> >> bash# sudo -u apache perl test.cgi.
>
> >> Please advise how to fix this. Thanks a lot.
>
> First, can you send e-mail through $smtpserver directly?
>
> Second, have die() show you why the method failed:
>
> my $smtp=new Net::SMTP($smtpserver, Timeout =>60)
> or die "Error for $smtpserver: $!";
>
> Third, try the Debug parameter.
------------------------------
Date: 18 May 2007 00:53:15 -0700
From: iulukus@gmail.com
Subject: Calling alarm more than once
Message-Id: <1179474795.611468.201970@h2g2000hsg.googlegroups.com>
Hi,
Is it possible to call the alarm more than once. If it is posible,
how?
I couldn't do it in my program:
{
.....
.....
RETRY:print "Send REQUEST to $server\n";
$payload = "x87\x00\x0c\x02\x1b\x62\x1f\x73\x96\x40\x68\x74\xfb\xff
\xff";
$lpayload = length($payload);
$dummy = syswrite($remote, $payload, $lpayload); # $remote is my UDP
socket.
print "Send REQUEST \n";
eval {
local $SIG{'ALRM'} = sub {print "abc";die "alarm\n"};
alarm 6;
sysread($remote, $result, 1024); # Read from socket
alarm 0;
};
if ($@) {
die unless $@ eq "alarm\n"; # propagate unexpected errors
goto RETRY;
# timed out
}
else {
print $@;
# didn't
}
OUTPUT:
Send REQUEST to 1.1.1.1
Send REQUEST
abcalarm
Send REQUEST to 1.1.1.1
Send REQUEST
For the second loop, program did not call the alarm subroutine and
program hang.
What can be the problem?
thanks in advance.
------------------------------
Date: Fri, 18 May 2007 10:04:23 +0100
From: Tim Southerwood <ts@dionic.net>
Subject: Re: Calling alarm more than once
Message-Id: <464d6c17$0$648$5a6aecb4@news.aaisp.net.uk>
iulukus@gmail.com wrote:
> Hi,
> Is it possible to call the alarm more than once. If it is posible,
> how?
Assuming you are doing this on a typical unix system...
No, unfortunately:
man -S2 alarm
...
DESCRIPTION
alarm() arranges for a SIGALRM signal to be delivered to the process
in seconds seconds.
If seconds is zero, no new alarm() is scheduled.
In any event any previously set alarm() is cancelled.
...
> I couldn't do it in my program:
No, but that's not an error. PITA, but expected.
I didn't have time to read your code, but in order to run multiple pending
alarms, one solution is to write your own multi-alarm
subroutine/module/class, which queues alarm requests. That class then uses
alarm() to time out to the next alarm scheduled to trip and does a callback
to a user supplied subroutine, after setting up the next alarm().
Beware of sleep() - that uses the same timer as alarm() so you may need to
emulate that. Also beware of random other modules that use alarm() or
sleep() internally.
As usual, someone already had this problem before you and CPAN to the
rescue:
http://search.cpan.org/~johnsca/libalarm-1.0/lib/Alarm/Queued.pm
Is that any use to you?
HTH
Tim
------------------------------
Date: 18 May 2007 02:38:07 -0700
From: filippo <filippo2991@virgilio.it>
Subject: Re: encoding problem on Tk entry widget
Message-Id: <1179481086.927290.257330@w5g2000hsg.googlegroups.com>
On 17 Mag, 10:45, Ch Lamprecht <ch.l.n...@online.de> wrote:
> filippo wrote:
>
> $dh->do("SET client_encoding TO 'UTF8'");
thanks today I will try it.
I understand that could be a encoding problem between db (latin9) and
windows (utf8).
I know it's of topic here, but do you know how can I convert my
database from LATIN9 to UTF8 to avoid such problems?
Thanks,
Filippo
------------------------------
Date: 17 May 2007 22:16:49 -0700
From: britneysspears1@gmail.com
Subject: Lindsay Lohans TITS! OOPSIE!
Message-Id: <1179465409.614660.249670@q23g2000hsg.googlegroups.com>
Download http://scargo.in Lindsay Lohans Tits free tits and videos!
MUST CLICK! I mean see.
------------------------------
Date: Fri, 18 May 2007 04:42:12 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri May 18 2007
Message-Id: <JI7zqC.s1o@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Business-OnlinePayment-TransFirsteLink-0.02
http://search.cpan.org/~jef/Business-OnlinePayment-TransFirsteLink-0.02/
Transfirst eLink backend for Business::OnlinePayment
----
Class-C3-XS-0.06
http://search.cpan.org/~blblack/Class-C3-XS-0.06/
XS speedups for Class::C3
----
Class-Data-Accessor-0.04001
http://search.cpan.org/~claco/Class-Data-Accessor-0.04001/
Inheritable, overridable class and instance data accessor creation
----
Data-Serializer-0.41
http://search.cpan.org/~neely/Data-Serializer-0.41/
Modules that serialize data structures
----
Data-Validate-Domain-0.07
http://search.cpan.org/~neely/Data-Validate-Domain-0.07/
domain validation methods
----
Data-Validate-Domain-0.08
http://search.cpan.org/~neely/Data-Validate-Domain-0.08/
domain validation methods
----
Data-Validate-IP-0.07
http://search.cpan.org/~neely/Data-Validate-IP-0.07/
ip validation methods
----
Date-Formatter-0.09
http://search.cpan.org/~stevan/Date-Formatter-0.09/
A simple Date and Time formatting object
----
Egg-Release-2.07
http://search.cpan.org/~lushe/Egg-Release-2.07/
Version of Egg WEB Application Framework.
----
Exception-Base-0.06
http://search.cpan.org/~dexter/Exception-Base-0.06/
Lightweight exceptions
----
Exception-System-0.06
http://search.cpan.org/~dexter/Exception-System-0.06/
The exception class for system or library calls
----
Exception-System-0.0601
http://search.cpan.org/~dexter/Exception-System-0.0601/
The exception class for system or library calls
----
File-Path-1.99_01
http://search.cpan.org/~dland/File-Path-1.99_01/
create or remove directory trees
----
Gearman-Client-Async-0.94
http://search.cpan.org/~bradfitz/Gearman-Client-Async-0.94/
Asynchronous client module for Gearman for Danga::Socket applications
----
I18N-Charset-1.383
http://search.cpan.org/~mthurn/I18N-Charset-1.383/
IANA Character Set Registry names and Unicode::MapUTF8 (et al.) conversion scheme names
----
I18N-Charset-1.385
http://search.cpan.org/~mthurn/I18N-Charset-1.385/
IANA Character Set Registry names and Unicode::MapUTF8 (et al.) conversion scheme names
----
MDV-Packdrakeng-1.10
http://search.cpan.org/~nanardon/MDV-Packdrakeng-1.10/
Simple Archive Extractor/Builder
----
Mail-SpamCannibal-0.79
http://search.cpan.org/~miker/Mail-SpamCannibal-0.79/
A tool to stop SPAM
----
ObjectDBI-0.06
http://search.cpan.org/~kjh/ObjectDBI-0.06/
Perl Object Serialization in an RDBMS using DBI
----
RT-Client-REST-0.29
http://search.cpan.org/~dmitri/RT-Client-REST-0.29/
talk to RT installation using REST protocol.
----
Regexp-Assemble-0.29
http://search.cpan.org/~dland/Regexp-Assemble-0.29/
Assemble multiple Regular Expressions into a single RE
----
Rose-Object-0.84
http://search.cpan.org/~jsiracusa/Rose-Object-0.84/
A simple object base class.
----
Safe-Caller-0.05
http://search.cpan.org/~schubiger/Safe-Caller-0.05/
A nicer interface to the built-in caller()
----
Term-Spinner-0.01
http://search.cpan.org/~blblack/Term-Spinner-0.01/
A progress spinner for commandline programs
----
WWW-Nike-NikePlus-0.02
http://search.cpan.org/~alexlomas/WWW-Nike-NikePlus-0.02/
Perl extension for retrieving running data from www.nikeplus.com
----
Win32-0.29
http://search.cpan.org/~jdb/Win32-0.29/
Interfaces to some Win32 API Functions
----
XML-Grammar-Screenplay-0.0101
http://search.cpan.org/~shlomif/XML-Grammar-Screenplay-0.0101/
module implementing an XML grammar for screenplays.
----
re-engine-Plugin-0.03
http://search.cpan.org/~avar/re-engine-Plugin-0.03/
API to write custom regex engines
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: 18 May 2007 07:10:15 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <464d5156$0$3582$ae4e5890@news.nationwide.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.7 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.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 that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_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: Fri, 18 May 2007 10:25:38 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Setting up YaBB Perl forum - weird respond as plain text in browser, including headers
Message-Id: <dgoq431p97cgqo8q6rngc32p70bgn79r5u@4ax.com>
On 17 May 2007 15:13:10 -0700, van100j@gmail.com wrote:
>I'm a real beginner to perl, and tried to start messing around with
>YaBB forum. It all went smooth on one server, but when I've tried to
You welcome. But this group is generally for discussing the Perl
programming language itself, not apps that happen to be written in
Perl. That is, there's the remote possibility that someone here is
familiar with this YaBB thingie and that she will want to help you.
But don't rely on that. Probably there are project-specific resources
where you're more likely to find the info you need. In particular in
your post there's no Perl code whatsoever and so most people here
won't comment at all.
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: 17 May 2007 22:26:12 -0700
From: forumgogo <forumgogo@gmail.com>
Subject: Support you the best free forum!
Message-Id: <1179465972.444050.67540@w5g2000hsg.googlegroups.com>
also ,its a spam.but if you need,come on .thank you .
support you the best free forum .www.forumgogo.com
Free Unlimited Storage
Free Unlimited Bandwidth
Free Free Subdomain
Free More Skins
Free No annoying pop-ups
Free 99% Uptime
Free Daily Backups
Free Fast, Friendly Tech Support
So,what's that?
That's our free forum named http://www.forumgogo.com
We have the human_based management also provide you human_based forum
service.
You needn't,we won't !
This is a great site that is completely free, and can make some cool
forums, here's an example of one, you can make your own topic, polls,
and replies etc, and you can have an accout for every member. This
next link is an example of a forum made from invisionfree.
http://support.forumgogo.com
------------------------------
Date: 18 May 2007 02:02:35 -0700
From: "Thomas J." <jue@monster-berlin.de>
Subject: Re: Year in two digits; Time with leading zero
Message-Id: <1179478954.991106.188100@w5g2000hsg.googlegroups.com>
Youre using "leading zero"-format for $currentdate, why not for
$currenttime ?
for 2-digit-date use the modulo-function (%)
$currentdate = sprintf("%02d/%02d/%02d", $day, $month+1, $year % 100);
$currenttime = sprintf("%02d:%02d", $hrs,$min);
hth, Thomas
------------------------------
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 V11 Issue 444
**************************************
