[22357] in Perl-Users-Digest
Perl-Users Digest, Issue: 4578 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Feb 18 00:05:38 2003
Date: Mon, 17 Feb 2003 21: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 Mon, 17 Feb 2003 Volume: 10 Number: 4578
Today's topics:
Re: (not 1) and (!1) yield zero length string <parv_fm@emailgroupsWhereElse.net>
Re: (not 1) and (!1) yield zero length string <parv_fm@emailgroupsWhereElse.net>
Re: (not 1) and (!1) yield zero length string <parv_fm@emailgroupsWhereElse.net>
DBD::CSV creates tables with column names in upper case (john harrold)
Re: DBD::CSV creates tables with column names in upper <goldbb2@earthlink.net>
Re: DBD::CSV creates tables with column names in upper <jeff@vpservices.com>
Re: DBD::CSV creates tables with column names in upper <jeff@vpservices.com>
Newbie Q re form to mail script FormProcessorPro <notworking@all.com>
Non-blocking file I/O, (jtd)
Re: Non-blocking file I/O, <goldbb2@earthlink.net>
parsing string with whitespace (Thomas Abraham)
Re: parsing string with whitespace (Tad McClellan)
Re: parsing string with whitespace (Jay Tilton)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Problem with SUID and DBD::DB2 <shah@typhoon.xnet.com>
Re: Regular Expression Noob <Jodyman@hotmail.com>
Re: Regular Expression Noob <goldbb2@earthlink.net>
Re: Sharing Variables and Functions Across Modules <hal@thresholddigital.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 18 Feb 2003 02:51:20 GMT
From: parv <parv_fm@emailgroupsWhereElse.net>
Subject: Re: (not 1) and (!1) yield zero length string
Message-Id: <slrnb53857.2kh.parv_fm@localhost.holy.cow>
in message <3E51003B.2000205@yahoo.com>,
wrote Salvador Fandiño García ...
> Eric J. Roode wrote:
...
> > What's wong with just ''?
>
> if you are using numbers it is not very consistent because
>
> !0 ==> 1 # ok
> !1 ==> '' # most people would expect 0
Exactly my point and problem: using a test result value like above
causes unexpected behaviour in calculations. One ugly workaround is
to OR the result w/ 0.
- parv
--
please don't send me private e-mail.
if you must, do away w/ WhereElse in the address.
------------------------------
Date: Tue, 18 Feb 2003 02:54:55 GMT
From: parv <parv_fm@emailgroupsWhereElse.net>
Subject: Re: (not 1) and (!1) yield zero length string
Message-Id: <slrnb538cg.2kh.parv_fm@localhost.holy.cow>
in message <b2qbfk$h3q$1@mamenchi.zrz.TU-Berlin.DE>,
wrote Anno Siegel ...
> In "(!0 && 0)", "!0" evaluates to something true, so the second
> operand (0) is returned. In "(!1 && 0)", "!1" evaluates to false,
> so the second operand isn't even looked at. The expression
> returns "!1", which prints as an empty string.
Thanks Anno, that explains the behaviour.
- parv
--
please don't send me private e-mail.
if you must, do away w/ WhereElse in the address.
------------------------------
Date: Tue, 18 Feb 2003 03:01:09 GMT
From: parv <parv_fm@emailgroupsWhereElse.net>
Subject: Re: (not 1) and (!1) yield zero length string
Message-Id: <slrnb538o6.2kh.parv_fm@localhost.holy.cow>
in message <3E50C3DF.7030801@yahoo.com>,
wrote Salvador Fandiño García ...
> parv wrote:
>
>> (Salvador's reply was similar.)
>
> no, it wasn't, I said:
>
> SF> It seems that (not 1) returns a magic scalar that renders as 0 in
> SF> numeric context and '' in other scalar contexts.
Sorry then. I must have not read the both replies very carefully.
- parv
--
please don't send me private e-mail.
if you must, do away w/ WhereElse in the address.
------------------------------
Date: 17 Feb 2003 18:51:47 -0800
From: jmh17@pitt.edu (john harrold)
Subject: DBD::CSV creates tables with column names in upper case..
Message-Id: <31d0e2b6.0302171851.6cbd4ec5@posting.google.com>
hey.
i'm not really sure what i'm doing wrong. i'm using the following sql
to create a flat file with the standard prepare and execute:
<sql>
CREATE TABLE transaction (
id int NOT NULL,
number int,
amount varchar(200),
description varchar(200),
timestamp int)
</sql>
the file that it creates looks like:
<file>
ID,NUMBER,AMOUNT,DESCRIPTION,TIMESTAMP
</file>
so my question is why does it change all of the column names to upper
case? is there any way to prevent this?
------------------------------
Date: Mon, 17 Feb 2003 22:54:57 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: DBD::CSV creates tables with column names in upper case..
Message-Id: <3E51AE91.F388CAA8@earthlink.net>
john harrold wrote:
>
> hey.
>
> i'm not really sure what i'm doing wrong. i'm using the following sql
> to create a flat file with the standard prepare and execute:
>
> <sql>
> CREATE TABLE transaction (
> id int NOT NULL,
> number int,
> amount varchar(200),
> description varchar(200),
> timestamp int)
> </sql>
>
> the file that it creates looks like:
>
> <file>
> ID,NUMBER,AMOUNT,DESCRIPTION,TIMESTAMP
> </file>
>
> so my question is why does it change all of the column names to upper
> case?
Because unless you quote the column names, that's what normally happens
in ANSI standard SQL.
> is there any way to prevent this?
Yes, I think so, but you would have to also quote the column names in
every single one of your sql queries, too -- it's a whole lot more work
on your part, and just not worth it.
--
$;=qq qJ,krleahciPhueerarsintoitq;sub __{0 &&
my$__;s ee substr$;,$,&&++$__%$,--,1,qq;;;ee;
$__>2&&&__}$,=22+$;=~y yiy y;__ while$;;print
------------------------------
Date: Mon, 17 Feb 2003 20:23:27 -0800
From: Jeff Zucker <jeff@vpservices.com>
Subject: Re: DBD::CSV creates tables with column names in upper case..
Message-Id: <3E51B53F.5070801@vpservices.com>
john harrold wrote:
> so my question is why does it change all of the column names to upper
> case? is there any way to prevent this?
The next version of SQL::Statement (1.006) which will be out within
about a week will correct this problem.
--
Jeff
------------------------------
Date: Mon, 17 Feb 2003 20:35:09 -0800
From: Jeff Zucker <jeff@vpservices.com>
Subject: Re: DBD::CSV creates tables with column names in upper case..
Message-Id: <3E51B7FD.8030402@vpservices.com>
Benjamin Goldberg wrote:
>>so my question is why does it change all of the column names to upper
>>case?
>>
>
> Because unless you quote the column names, that's what normally happens
> in ANSI standard SQL.
Actually ANSI standard specifies only that the column names be *treated*
as case insensitive and doesn't specify what case they are *stored* in.
Previous versions of SQL::Statement used IC_MIXED (identifiers are
treated as case insensitive in SQL and stored in mixed case) but the
current version (1.005) is IC_UPPER (case insensitve treatment and
stored in UPPER). It will revert to its previous behaviour in version
1.006.
Users who are interested in maximum portability shouldn't count on the
case of the identifiers since there is variability between SQL
implementations and should use instead things like NAME_lc and NAME_uc
to force a case.
None of this applies to quoted identifiers which are always mixed case
and (as Benjamin points out) somewhat of a pain to deal with.
--
Jeff
------------------------------
Date: Tue, 18 Feb 2003 02:36:28 -0000
From: Trilby <notworking@all.com>
Subject: Newbie Q re form to mail script FormProcessorPro
Message-Id: <MPG.18bbac702e3f5e759896cf@news.iol.ie>
Hi all,
I am not a perl programmer but trying to deal with a perl script called
FormProcessorPro v3.2 [Mitridat.com] which takes the contents of a html
form and emails it to recipients in a format based on templates that the
user can set out in a txt file with whatever text is required and the
fields from the form in brackets [ ].
I am hoping you can help me with a small matter:
I have the script working fine for a while now... except the text
formatting of the resulting email created from the form.
The email template begins:(after the email header)
Name of Registree
[name]
============<>===========
Position of Registree
[position]
============<>===========
Company name
[company]
============<>===========
Email address
[re_email]
============<>===========
Address:
[address1]
[address2]
[address3]
============<>===========
Telephone contact no.
[telephone]
============<>===========
Fax no.
[fax]
============<>===========
[continues with more fields]
And the resulting email begins:
===beginning of form outp
ut===NameofRegistreeDavidMurphy=======================PositionofRegistre
eBoss=======================CompanynameAnchor=======================Emai
laddressuser@netbox.zl6
=======================AddressLondon=======================Telephonecont
act no.
555 66666
============<>===========
Where the lines are continuous for the first few entries and not limited
by my usenet app. The lay out corrects itself after the 't' of
telephonecontact and the rest of the content is formatted correctly.
Is there a way to fix this ? is there any significance in the use of
'-' or '=' characters that could be messing things up ?
Note the fact that in the email address field the entered address of
user@netbox.zl6 appears when the actual address entered was
user@netbox.com
Much obliged,
Trilby
------------------------------
Date: 17 Feb 2003 18:08:05 -0800
From: adwser@hotmail.com (jtd)
Subject: Non-blocking file I/O,
Message-Id: <c57c103.0302171808.6fee1a1@posting.google.com>
What is the best way to do non-blocking file I/O? Select? I'm
interested in parallelizing reads from multiple disks (writes are less
important since there's write caching). I thought about having a
server per disk, and have a master server select on socket connections
to the disk servers, but that looks messy.
A related question is, suppose I use raid 5 (3ware escalade), will
that affect my ability to parallelize reads?
Thanks!
------------------------------
Date: Mon, 17 Feb 2003 22:50:30 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: Non-blocking file I/O,
Message-Id: <3E51AD86.3AB41827@earthlink.net>
jtd wrote:
>
> What is the best way to do non-blocking file I/O? Select?
Unfortunatly, select() will *always* indicate that a a disk file is
readable, regardless of whether or not the OS has prefetched data from
that file.
You have essentially two choices:
1/ Use IO::File objects as your handles, and use the ->blocking()
method to deactivate the normal blocking behavior of reading. You'll
probably want to use sysread(), instead of read()/readline()/<>, in
order to differentiate between an error due to EWOULDBLOCK from other
types of errors. The major disadvantage of this technique is that
you'll have to poll your handles continuously, busy-looping until data
is ready -- blech.
2/ Create one thread for each handle, each of which performs an
ordinary blocking read, using any of read(),readline(),<>, or sysread().
The disadvantages of this is that threads.pm is only available with
perl5.8.0, and perl threads are not lightweight -- creating a perl
thread is sortof like forking a process, but slower. The major
advantage of this is that there's no busy-looping; each worker thread is
performing ordinary blocking IO, and the main thread uses lock/cond_wait
to sleep until one of the threads successfully reads some data.
There's also sortof a third option -- for each file, create a *process*
which opens that file, reads from the disk, and sends the output to a
pipe. You can then use select() on the pipes from each of the child
processes.
> I'm interested in parallelizing reads from multiple disks (writes are
> less important since there's write caching). I thought about having a
> server per disk, and have a master server select on socket connections
> to the disk servers, but that looks messy.
A server? Sockets? Sounds vaguely like the option 3 I was thinking of,
except that you're probably thinking of something significantly more
complicated (and messy) than I'm thinking of.
My idea (the one for using multiple processes) is:
my @files = .....; # the filenames.
my %info;
my $sel = IO::Select->new;
for my $name (@files) {
pipe( my ($rd, $wr) ) or horribly;
defined(my $pid = fork) or die horribly;
if( $pid ) {
$sel->add($rd);
$info{$rd} = [$name, $pid];
next;
}
close $rd;
open( my ($fh), "<", $name ) or die horribly;
$| = 1, select $_ for select $wr;
$! = 0;
print $wr $_ while my $n = sysread $fh, $_, 512;
die "Error reading from $name: $!" if !defined $n;
exit;
}
while( my @ok = $sel->can_read ) {
....
}
[untested]
> A related question is, suppose I use raid 5 (3ware escalade), will
> that affect my ability to parallelize reads?
I have no clue.
--
$;=qq qJ,krleahciPhueerarsintoitq;sub __{0 &&
my$__;s ee substr$;,$,&&++$__%$,--,1,qq;;;ee;
$__>2&&&__}$,=22+$;=~y yiy y;__ while$;;print
------------------------------
Date: 17 Feb 2003 20:08:13 -0800
From: thomas_rp@hotmail.com (Thomas Abraham)
Subject: parsing string with whitespace
Message-Id: <5cf0e3b0.0302172008.67b146a2@posting.google.com>
Hi,
How can I convert the following string:
spacespacespaceHellospacespaceWorld!spacespacespacespace
into an array that contains the following elements
item[0] = spacespacespace
item[1] = Hello
item[2] = spacespace
item[3] = World!
item[4] = spacespacespacespace
where space stands for whitespace? Please note that I *need* the
number spaces (not trim it).
Thanks,
-Thomas
------------------------------
Date: Mon, 17 Feb 2003 23:00:02 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: parsing string with whitespace
Message-Id: <slrnb53fei.1sh.tadmc@magna.augustmail.com>
Thomas Abraham <thomas_rp@hotmail.com> wrote:
> How can I convert the following string:
>
> spacespacespaceHellospacespaceWorld!spacespacespacespace
>
> into an array that contains the following elements
>
> item[0] = spacespacespace
> item[1] = Hello
> item[2] = spacespace
> item[3] = World!
> item[4] = spacespacespacespace
my(undef ,@item) = split /((?:space)+)/;
> where space stands for whitespace?
my(@items) = /(\s+|\S+)/g;
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Tue, 18 Feb 2003 05:03:12 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: parsing string with whitespace
Message-Id: <3e51bdfb.122230198@news.erols.com>
thomas_rp@hotmail.com (Thomas Abraham) wrote:
: How can I convert the following string:
:
: spacespacespaceHellospacespaceWorld!spacespacespacespace
:
: into an array that contains the following elements
:
: item[0] = spacespacespace
: item[1] = Hello
: item[2] = spacespace
: item[3] = World!
: item[4] = spacespacespacespace
:
: where space stands for whitespace? Please note that I *need* the
: number spaces (not trim it).
@item = $foo =~ /(\s+|\S+)/g;
------------------------------
Date: Mon, 17 Feb 2003 22:42:48 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.3 $)
Message-Id: <8L2dnQ84-OxVJMyjXTWcpQ@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.3 $)
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.perl.com/CPAN-local/authors/Dean_Roehrich/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* 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: Tue, 18 Feb 2003 04:04:57 +0000 (UTC)
From: Hemant Shah <shah@typhoon.xnet.com>
Subject: Problem with SUID and DBD::DB2
Message-Id: <b2sbd9$h4k$1@flood.xnet.com>
Folks,
I am having problem with my perl script using DBD::DB2.
I have a perl script that scans a file and updates the DB2 database.
The script is called from an SUID program (SUID user is not root).
I have several AIX systems (two J50, H70) running AIX 4.3.3 and perl 5.6.0,
DB2 UDB 7.2 latest fix pack (7.1.0.72), DBI::DBD 10.7,
and DBD::DB2 0.75. The perl script is working fine on these systems.
Recently we purchased new AIX system (P630) with AIX 5.1, it is running
exact same version of perl, DBI, DBD and DB2. When the perl script is called
from a SUID program I get following error on first insert:
Can't bind unknown parameter marker '2' at
+/g2/gblcode/cob/sec/dynlib/LIDP/GblCodeDB.pm line 987, <GBLFILE> line 10
If I run the script from command line, then it executed fine. I put
debugging statements in the script and I can see that all the values are
properly defined.
Why would perl script fail in SUID mode on AIX 5.1?
Here are relevant statements:
$InsertStmt_CodeType = "INSERT INTO GBLCODE.CODETYPE
(SRC_NUM, CODE_TYPE)
VALUES
(?, ?)
;";
$InsertStmt_CodeType_Hdl = $DbHandle->prepare($InsertStmt_CodeType);
$InsertStmt_CodeType_Hdl->execute($SourceNum, $CodeType);
I get the error on execute statement. I print the value of SourceNum and
CodeType before execute statement, and they are valid.
Has anyone experienced same problem?
Thanks.
--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: NoJunkMailshah@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
------------------------------
Date: Tue, 18 Feb 2003 02:15:16 GMT
From: "Jodyman" <Jodyman@hotmail.com>
Subject: Re: Regular Expression Noob
Message-Id: <UGg4a.8162$YU4.697457@newsread1.prod.itd.earthlink.net>
"Z" <ztamir@yahoo.com> wrote in message
> I'm new to regular expressions and need a little help. What regular
> expression do I use within the PHP function split() to create an array
> of all the substrings located between ANI="TheNumberIwantIsHere"&
>
> The string I'm trying to parse looks like the following:
>
>
ANI=1114875732&NAME=Albert&EXT=3030&LOGIN=LoggedIn&TALK=Unavailable&PRIORITY
=2003-02-17
> 12:22:40 **==+==**ANI=222650654&NAME=Ami&EXT=3034&LOGIN=Logged
> In&TALK=Unavailable&PRIORITY=2003-02-17 12:35:08
> **==+==**ANI=3336600734&NAME=Louisa&EXT=3035&LOGIN=Logged
> In&TALK=Unavailable&PRIORITY=2003-02-17 12:37:20
> **==+==**ANI=4443830235&NAME=Roxanne&EXT=3032&LOGIN=Logged
> In&TALK=Unavailable&PRIORITY=2003-02-17 12:39:33
> **==+==**ANI=5556235414&NAME=Tia&EXT=3031&LOGIN=Logged
> In&TALK=Unavailable&PRIORITY=2003-02-17 12:38:13 **==+==**Total
> Agents=5 FINISHED
>
> So, in other words, starting from the first ANI I want to create an
> array that looks like this
>
> 1114875732
> 222650654
> 3336600734
> 4443830235
> 5556235414
>
use strict;
use warnings;
my ($results, @results);
while (<DATA>) {
($results) = $_ =~ (m/ANI=([0-9]+)&/);
print "\$_=$_\n";
print "\$results = $results\n";
push @results, $results if ($results);
}
for (@results) { print "$_\n"; }
__DATA__
ANI=1114875732&NAME=Albert&EXT=3030&LOGIN=LoggedIn&TALK=Unavailable&PRIORITY
=2003-02-17
12:22:40 **==+==**ANI=222650654&NAME=Ami&EXT=3034&LOGIN=Logged
In&TALK=Unavailable&PRIORITY=2003-02-17 12:35:08
**==+==**ANI=3336600734&NAME=Louisa&EXT=3035&LOGIN=Logged
In&TALK=Unavailable&PRIORITY=2003-02-17 12:37:20
**==+==**ANI=4443830235&NAME=Roxanne&EXT=3032&LOGIN=Logged
In&TALK=Unavailable&PRIORITY=2003-02-17 12:39:33
**==+==**ANI=5556235414&NAME=Tia&EXT=3031&LOGIN=Logged
In&TALK=Unavailable&PRIORITY=2003-02-17 12:38:13 **==+==**Total
Agents=5 FINISHED
#This works
#Jody
------------------------------
Date: Mon, 17 Feb 2003 22:13:45 -0500
From: Benjamin Goldberg <goldbb2@earthlink.net>
Subject: Re: Regular Expression Noob
Message-Id: <3E51A4E9.ACE13874@earthlink.net>
Z wrote:
>
> I'm new to regular expressions and need a little help. What regular
> expression do I use within the PHP function split() to create an array
> of all the substrings located between ANI="TheNumberIwantIsHere"&
You don't want to use split, you want to perform a match.
$data = "&" . $data;
$matches = preg_match_all( "/&ANI=([^&]*)/", $data)
[I think.... this is the right syntax for the regex, but I'm not sure
about the php syntax]
--
$;=qq qJ,krleahciPhueerarsintoitq;sub __{0 &&
my$__;s ee substr$;,$,&&++$__%$,--,1,qq;;;ee;
$__>2&&&__}$,=22+$;=~y yiy y;__ while$;;print
------------------------------
Date: Tue, 18 Feb 2003 03:48:29 GMT
From: Hal Vaughan <hal@thresholddigital.com>
Subject: Re: Sharing Variables and Functions Across Modules
Message-Id: <h2i4a.157003$be.140925@rwcrnsc53>
Gunnar Hjalmarsson wrote:
<snip>
> also makes the namespaces from ModB and ModC available as well.
>
> There is no longer any ModX namespace. Only main.
>
>> I had also tried, as you suggested, a direct reference:
>>
>> (from ModB):
>>
>> ModA::modasub("Called from ModB");
>>
>> And was getting Undefined Subroutine errors from that as well.
>
> ModA::modasub() calls the subroutine modasub() in *package* ModA. Since
> there is no longer such a package, that error message can be expected.
>
> An alternative solution, if the only thing you want to do is to split
> the module into several *files*, is to include the 'package ModA;'
> declaration at the top of all the files.
>
> / Gunnar
Actually, I didn't like that result (about everything in the same
namespace), so I started experimenting around and found that just putting
"package ModA;" at the beginning of the first file seemed to have that same
effect -- separating the namespace of the module(s) from the namespace of
the program itself.
It's working fine now and the program doesn't seem to have access to the
namespace of the modules (except for what's exported).
I'll also try adding the declaration on each of the new files I've split it
into and see what it does.
Thanks for a useful and helpful suggestion!
Hal
------------------------------
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 4578
***************************************
