[22861] in Perl-Users-Digest
Perl-Users Digest, Issue: 5082 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jun 6 06:05:48 2003
Date: Fri, 6 Jun 2003 03:05:07 -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, 6 Jun 2003 Volume: 10 Number: 5082
Today's topics:
Re: a Bayesian intelligent e-mail autoresponder? (Western Larch)
ANSI NT W2K <clandos@gmx.de>
Re: Changing form output (Steve)
Re: Changing form output <noreply@gunnar.cc>
Re: Daemon Script n' system() function - for gurus: Ran (Euler)
Re: DBD::Sybase and stored procedures <peter.dintelmann@dresdner-bank.com>
Re: Email Extraction (Graham Smith)
Re: free GUI win32? <jurgenex@hotmail.com>
Re: Help fixing my code needed (Mark Smith)
Re: Help needed checking if paths are the same (Mark Smith)
Re: perl <jurgenex@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Push adding space to start of items <jurgenex@hotmail.com>
Re: Push adding space to start of items (Mark Smith)
Re: Time limit <jurgenex@hotmail.com>
Re: Time limit <uri@stemsystems.com>
Re: UK script writer wanted <dha@panix.com>
Re: Upload without cgi.pm or cgi-lib <michael@shawcable.net>
Re: Upload without cgi.pm or cgi-lib <ubl@schaffhausen.de>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 5 Jun 2003 22:25:02 -0700
From: larix_occidentalis@yahoo.com (Western Larch)
Subject: Re: a Bayesian intelligent e-mail autoresponder?
Message-Id: <6869c57c.0306052125.6604a6c5@posting.google.com>
totojepast@atlas.cz (totojepast) wrote:
> I want the script to return an information based on the text of the
> query. Fighting spam is not the purpose.
Oh, OK. Well, the general outline is the same. You need to combine
probabilities with costs to figure out which action has the least
expected cost, and execute that action. If there are not too many
possible states and actions, I think you'll find it easy to script.
In more detail, here's what you need. Suppose you can compute
p(message type = 1|text), ..., p(message type = m|text).
For each message type, there's an appropriate response, I'm assuming.
Let a_1, ..., a_n represent the different responses. Note that n != m
in general, and "do nothing" can be one of the responses. You need
to assess cost(a_i, message type = j). Presumably an inappropriate
response costs you something, maybe a lot, and you get a reward for
an appropriate response. If constructing a cost matrix seems like
too much work, bear in mind that if you can't assess costs and rewards,
you have no rational basis for saying one action is better than another.
Now you have all the pieces. Compute
expected cost i = sum_{j=1}^m p(msg type = j|text) cost(a_i,msg type = j),
and pick i such that expected cost i is the least, and send response a_i.
You're all done!
The hard part is computing the probability of the message type.
In spam filtering, there are just two kinds of messages, but you
are working with several or many kinds. The same principals apply,
and the same range of models should be applicable.
Good luck and have fun!
L.
------------------------------
Date: Fri, 6 Jun 2003 11:31:29 +0200
From: "Carsten L." <clandos@gmx.de>
Subject: ANSI NT W2K
Message-Id: <3ee05f76$0$10140$4d4ebb8e@read.news.de.uu.net>
I try to make my output more colourful. But with Windows NT / 2000 I cant
use the ansi function described in the perl (5.6.1) documentation. I always
get the control sequence "?[1;34mThis text is bold blue."
Thanks for your help
carsten
------------------------------
Date: 5 Jun 2003 22:11:09 -0700
From: techadmin@shaw.ca (Steve)
Subject: Re: Changing form output
Message-Id: <2e27f51a.0306052111.b8e1ba8@posting.google.com>
Gunnar, bored are you? If you don't want to help then don't bother
responding, your just using up more than your fair share of the
internet.
Thanks,
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote in message news:<bbo369$bmeae$1@ID-184292.news.dfncis.de>...
> Steve wrote:
> > I am using BigNoseBird version 4 CGI script to process form
> > information.
>
> <snip>
>
> > is there a way to present it in the following format,
> >
> > Client ABC Enterprises
> > Address 123 Anywhere,
> > Canada
> > Instructions akjhdfajhfkajhflkjhasdjfh
> > asdfjsdfkjasdfkja;skjfkasjd
> > adfajsdfkjaskdjfakjsdflkja
>
> Yes.
>
> > I understand that changes need to be made to the code beloew
>
> Remarkable insight!
>
> > but all the books I have read do not give me the know how to make
> > the appropriate changes.
>
> Oh. Neither of them? Which books were they?
>
> Ever considered to make some own effort?
>
> / Gunnar
------------------------------
Date: Fri, 06 Jun 2003 10:03:15 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Changing form output
Message-Id: <bbphsj$c86ip$1@ID-184292.news.dfncis.de>
Steve wrote:
> Gunnar, bored are you?
This is how I read your question:
"I downloaded this free script. It doesn't quite satisfy my needs, and
I'm not interested in learning Perl, so could somebody modify the
script for free?"
Such questions do make me bored, and I don't want to see them in this
group. To prevent such reactions, you'd better show that you have
really tried yourself before posting.
/ Gunnar
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: 5 Jun 2003 21:43:19 -0700
From: eulerpereira@hotmail.com (Euler)
Subject: Re: Daemon Script n' system() function - for gurus: Randal L. Schwartz, Larry Wall, Joseph N. Hall, and others
Message-Id: <f94db63e.0306052043.2fdf29b4@posting.google.com>
Steve Grazzini <grazz@pobox.com> wrote in message news:<wpLDa.10841$b8.7398@nwrdny03.gnilink.net>...
> Euler <eulerpereira@hotmail.com> wrote:
> > Steve Grazzini <grazz@pobox.com> wrote:
> >> Euler <eulerpereira@hotmail.com> wrote:
> >> > but when i try execute system( 'system_command' ) function from
> >> > daemon, the return code ( $? ) from system() is -1. The same happens
> >> > when i try use quotation `system_command` or exec( 'system_command' ).
> >> >
> >> > but, the command is executed sucefully!!! What's wrong?
> >>
> >> Try to come up with a short[*] script that actually demonstrates
> >> the problem you're having.
> >
> > thanx for responding my question Steve, my apologies here's the
> > output:
> >
> > Thu Jun 5 10:03:18 2003 zeus daemon [debug] Starting...
> > Thu Jun 5 10:03:18 2003 zeus daemon [debug] PID: 15842
> > Thu Jun 5 10:03:18 2003 zeus daemon [debug] Command Executed: -1: No
> > child processes
> >
> > The last line point to the command executed sucefully ( this is truth,
> > i try use 'touch /foo.foo' instead 'ls' and '/foo.foo' is created each
> > 60 seconds, but the return code maintain -1 (Return value of -1
> > indicates a failure to start the program - help manpage).
>
> That looks like an error and return value from wait(). And you had a
> looping $SIG{CHLD} handler, so it's possible that the $? and $! you see
> have nothing to do with system().
>
> In fact, if -- going above and beyond the call of duty -- I change your
> main loop to look like this:
>
> if ( !system("touch ~/foo.pid") ) {
> _log(_msg(Command Executed: $?: $!\n":
> }
> else {
> _log(_msg(Command Failed: $?: $!\n":
> }
>
> I get exactly the output you describe. But this doesn't mean that
> system() failed or returned -1; it has actually returned zero, but
> I printed $? in the wrong branch.
hey guy, you pointed the solution, i comment line 25 -> $SIG{CHLD}
handler, so $? return 0 on succesful and -1 on error. The problem is
if child process send kill signal to parent (demon) process.
thanx,
Euler
------------------------------
Date: Fri, 6 Jun 2003 11:19:02 +0200
From: "Peter Dintelmann" <peter.dintelmann@dresdner-bank.com>
Subject: Re: DBD::Sybase and stored procedures
Message-Id: <bbpl33$meo2@news-1.bank.dresdner.net>
Hi Kevin,
"Kevin Healey" <newgroups@healeysonline.com_SPAMMENOT> wrote in message
news:OiHDa.105$fh.19@news2.east.cox.net...
> I am having some trouble preparing and executing a Sybase stored procedure
> using DBI.
>
> My stored procedure has a numeric output parameter, and I would like to
> use placeholders so that I can prepare the procedure once and call it
> multiple
> times.
the DBD::Sybase manpage on my system states that
you can't.
For those of you who are used to Transact-SQL there are
some limitations to using this feature: In particular you
can not pass parameters this way to stored procedures...
Regards,
Peter Dintelmann
------------------------------
Date: 6 Jun 2003 00:18:06 -0700
From: grehom@ntlworld.com (Graham Smith)
Subject: Re: Email Extraction
Message-Id: <98eb7f13.0306052318.1bc726b@posting.google.com>
You forgot to include the line:
use Win32::OLE::Variant;
up at the top of the program,
I deleted this line from the script I wrote for you and the error you
mention was the only error I got with my data.
G
ksu1wd@mit.edu (Avatar) wrote in message news:<415d5171.0306050837.fad2eae@posting.google.com>...
> > print "Received:", $message->{ReceivedTime}, "\n";
> that returns Received:Win32::OLE::Variant=SCALAR(0x1a4a9e0)
> I think that is hex
> But how do we go from that to decimal?
------------------------------
Date: Fri, 06 Jun 2003 05:35:55 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: free GUI win32?
Message-Id: <%KVDa.53690$Pb.15506@nwrddc01.gnilink.net>
Daniel L Newhouse wrote:
> I have been told that there is a free GUI that can be downloaded for
> Perl on Windows. I have already installed the free ActiveState
> ActivePerl 5.8 msi package.
Well, Perl-TK comes to mind.
I'm sure there are others.
jue
------------------------------
Date: 6 Jun 2003 02:42:59 -0700
From: Mark.Smith@sonyericsson.com (Mark Smith)
Subject: Re: Help fixing my code needed
Message-Id: <cf24885e.0306060142.78e24b39@posting.google.com>
"Jürgen Exner" <jurgenex@hotmail.com> wrote in message news:<BLHDa.47343$da1.6938@nwrddc03.gnilink.net>...
> Mark Smith wrote:
> [...]
> > match. Now I need to disregard the drive letter and case so I would
> > get a match for the following strings:
> >
> > d:\path\somepath\path1\filename.exe
> >
> > and
> >
> > \PATH\somepath\Path1\Filename.exe
>
> A very typical algorithmic question that has little to do with Perl (you
> would use the same approach in any other programming language, too).
> The solution is trivial: define a normal form, tranform both(!) values into
> the normal form, and compare them.
>
> In your case:
> - normal form: you could use e.g. no drive letter and path all upper case
> (just an example).
> - the write a function that converts any path into normal form:
>
> normalform { #untested, for illustration only
> $_[0] =~ s/^.://;
> return uc($_[0]);
> }
>
> - and then simply compare your names
>
> if (normalform($file1) eq normalform($file2)) {
> print "The names $file1 and $file2 are the same\n";
> }
>
> jue
Hi,
Came up with a solution which is pretty much exactly what you said but
without using a subroutine. Only one of the two files had contents
that contained drive letters so it didn't seem necessary to write sub.
Thanks for your feedback.
Regards,
Mark.
------------------------------
Date: 6 Jun 2003 02:38:12 -0700
From: Mark.Smith@sonyericsson.com (Mark Smith)
Subject: Re: Help needed checking if paths are the same
Message-Id: <cf24885e.0306060138.390f4677@posting.google.com>
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote in message news:<bbn564$b2oi5$1@ID-184292.news.dfncis.de>...
> Mark Smith wrote:
> > I have two arrays of file paths. One contains paths in the format:
> >
> > d:\path\somepath\path1\filename.exe
> >
> > The other contains paths in the format:
> >
> > \Path\ANOTHERPATH\Pathname\somefile.txt
>
> <snip>
>
> > I perform the comparison with:
> >
> > if ( $envpath =~ m/$path/i )
> >
> > However at this line I get the error:
> > Can't find unicode character property definition via main->W or
> > W.pl at C:\Perl\bin\dev\failed_source\extract_failed.pl line 70
>
> You need to quote the backslashes in the pattern:
>
> if ( $envpath =~ m/\Q$path/i )
> -----------------------^^
>
> / Gunnar
Thanks for your response.
Found a problem when using pattern matching meant I sometimes matched
incorrectly. Now got it working by stripping off the drive
information, converting strings to lowercase and then testing for
equivalence.
Mark
------------------------------
Date: Fri, 06 Jun 2003 05:42:06 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: perl
Message-Id: <OQVDa.53736$Pb.413@nwrddc01.gnilink.net>
C Marshall wrote:
> tadmc@augustmail.com (Tad McClellan) wrote in message
>> Have you seen the docs about Perl books?
>>
>> perldoc -q book
>>
>> perldoc perlbook
>
> Crikey - is there no end to what is available under perldoc ?
> The guys who maintain that must be costing Oreilly a fortune
Where did you get the idea that the authors of perldoc are paid by OReilly?
I'm sure they would very much appreciate that additional funding, but it
ain't that way.
jue
------------------------------
Date: Fri, 06 Jun 2003 02:25:45 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <V-WcnapxgZ9k3H2jXTWcqQ@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, 06 Jun 2003 05:43:45 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Push adding space to start of items
Message-Id: <lSVDa.53750$Pb.4656@nwrddc01.gnilink.net>
Mark Smith wrote:
> Can anyone help me. I'm processing some information. If it meets a
> condition I push the value (and \n) onto an array. If I output the
> array, after the first line I get a space on every newline.
>
> Why is this happening and how can I stop it? It is not from the
> values I put in the array.
I wonder if this is just an odd way to ask the Frequently Asked Question:
"Why do I get weird spaces when I print an array of lines?"
jue
------------------------------
Date: 6 Jun 2003 02:46:30 -0700
From: Mark.Smith@sonyericsson.com (Mark Smith)
Subject: Re: Push adding space to start of items
Message-Id: <cf24885e.0306060146.16cecb0e@posting.google.com>
"Jürgen Exner" <jurgenex@hotmail.com> wrote in message news:<lSVDa.53750$Pb.4656@nwrddc01.gnilink.net>...
> Mark Smith wrote:
> > Can anyone help me. I'm processing some information. If it meets a
> > condition I push the value (and \n) onto an array. If I output the
> > array, after the first line I get a space on every newline.
> >
> > Why is this happening and how can I stop it? It is not from the
> > values I put in the array.
>
> I wonder if this is just an odd way to ask the Frequently Asked Question:
> "Why do I get weird spaces when I print an array of lines?"
>
> jue
Sorry about the poor description of the problem. Was rushing as I was
leaving work and did a bit of a brain dump. Problem now solved and
yes I was using quotes around the array, removed them and all is now
well in the World. You live and you learn.
Regards,
Mark.
------------------------------
Date: Fri, 06 Jun 2003 05:46:35 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: Time limit
Message-Id: <%UVDa.53773$Pb.53689@nwrddc01.gnilink.net>
Zvezdoshka@nowhere.ru wrote:
> In a quizz, I want setup a time limit for users to reply to each
> question. What's the best way to do this ?
Did you see the FAQ "How do I timeout a slow event?"
> A cookie that expires in xx
> seconds, is that the only way ?
Perl has cookies? Interesting....
jue
------------------------------
Date: Fri, 06 Jun 2003 05:54:16 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Time limit
Message-Id: <x7d6hrbvjs.fsf@mail.sysarch.com>
>>>>> "JE" == Jürgen Exner <jurgenex@hotmail.com> writes:
JE> Perl has cookies? Interesting....
well, perl6 has PMCs :)
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Fri, 6 Jun 2003 04:46:25 +0000 (UTC)
From: "David H. Adler" <dha@panix.com>
Subject: Re: UK script writer wanted
Message-Id: <slrnbe0751.khg.dha@panix2.panix.com>
In article <MPG.194993791dde396d98adf7@news.newshosting.com>, Cannabis
Coffee Shops wrote:
> Sort of off topic as its not a perl question - but as somebody on here
> will earn money from doing it I reckon its ok .
You have posted a job posting or a resume in a technical group.
Longstanding Usenet tradition dictates that such postings go into
groups with names that contain "jobs", like "misc.jobs.offered", not
technical discussion groups like the ones to which you posted.
Had you read and understood the Usenet user manual posted frequently to
"news.announce.newusers", you might have already known this. :) (If
n.a.n is quieter than it should be, the relevent FAQs are available at
http://www.faqs.org/faqs/by-newsgroup/news/news.announce.newusers.html)
Another good source of information on how Usenet functions is
news.newusers.questions (information from which is also available at
http://www.geocities.com/nnqweb/).
Please do not explain your posting by saying "but I saw other job
postings here". Just because one person jumps off a bridge, doesn't
mean everyone does. Those postings are also in error, and I've
probably already notified them as well.
If you have questions about this policy, take it up with the news
administrators in the newsgroup news.admin.misc.
http://jobs.perl.org may be of more use to you
Yours for a better usenet,
dha
--
David H. Adler - <dha@panix.com> - http://www.panix.com/~dha/
I expect my version of ESP::Psychic will be ready sometime last week.
More likely, yesterday (you know how schedules tend to slip).
- Eric The Read in comp.lang.perl.misc
------------------------------
Date: Fri, 06 Jun 2003 06:31:27 GMT
From: michael <michael@shawcable.net>
Subject: Re: Upload without cgi.pm or cgi-lib
Message-Id: <3zWDa.161265$Vi5.4605929@news1.calgary.shaw.ca>
GhostNr1 <ghostnr1@telia.com> wrote:
> I have a mysql database and then I have a text file that should be uploaded.
> Ether it should be uploaded to the database or uploaded to a directory and
> it should be done a link to it via sql. I just can't find any upload that is
> not useing cgi.pm becouse I don't use that and I don't whant to use it.
> thx GhostNr1
The words you use are not the correct words, so it is hard to know what
you want to do.
You have a mysql database on what computer?
You have a text file on what computer?
What do you need to do? You want to transfer the data in the text file into
the data base?
What sort of tool do you want the user to use? Do you want them to
use a browser to upload the data, or does this have nothing to do with the
web (i.e. you want them to run a command line program to move a text
file into a database?).
------------------------------
Date: Fri, 06 Jun 2003 11:23:04 +0200
From: Malte Ubl <ubl@schaffhausen.de>
Subject: Re: Upload without cgi.pm or cgi-lib
Message-Id: <bbppma$oed$1@news.dtag.de>
GhostNr1 wrote:
> I have a mysql database and then I have a text file that should be uploaded.
> Ether it should be uploaded to the database or uploaded to a directory and
> it should be done a link to it via sql. I just can't find any upload that is
> not useing cgi.pm becouse I don't use that and I don't whant to use it.
> thx GhostNr
Read the spec:
http://hoohoo.ncsa.uiuc.edu/cgi/
http://www.google.de/search?hl=de&ie=ISO-8859-1&q=http+spec&meta=
I wish you best of luck.
malte
PS: I think your stupid.
------------------------------
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 5082
***************************************
