[24163] in Perl-Users-Digest
Perl-Users Digest, Issue: 6355 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 2 06:06:10 2004
Date: Fri, 2 Apr 2004 03:05:07 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 2 Apr 2004 Volume: 10 Number: 6355
Today's topics:
Re: "which perl": Different for root and users <footnipple@indiatimes.com>
Re: "which perl": Different for root and users (Lack Mr G M)
bash shell script - perl conversion (Peter Steele)
Re: Boxed Perl or ActiveState Perl? <bart.lateur@pandora.be>
Re: DBI:mysql and huge tables <t.goetz@dkfz.de>
Re: free source for bbs <lawshouse.public@btconnect.com>
How do I do when handling the data <letnomanenterhere@yahoo.co.kr>
Re: How do I do when handling the data <noreply@gunnar.cc>
Re: include different files at run time <tore@aursand.no>
Re: multidimensional hash copy problem <uri.guttman@fmr.com>
Re: Need help with a Perl Script Error <tadmc@augustmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: test (Ken Blau Original Author)
Re: Tough (for me) regex case <brian@knowdotnet.nospam.com>
Re: uninitialized value in concatenation ... <uri.guttman@fmr.com>
Re: uninitialized value in concatenation ... <postmaster@castleamber.com>
Win32::FileSecurity doesn't show all perms? <perlcdr@mail.rumania>
Re: Win32::FileSecurity doesn't show all perms? <wherrera@lynxview.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 02 Apr 2004 03:09:50 GMT
From: "sdfgsd" <footnipple@indiatimes.com>
Subject: Re: "which perl": Different for root and users
Message-Id: <2Q4bc.375121$B81.5552032@twister.tampabay.rr.com>
"John W. Krahn" <krahnj@acm.org> wrote in message
news:406C9C00.EC9884C0@acm.org...
> sdfgsd wrote:
> >
> > "Anno Siegel" <anno4000@lublin.zrz.tu-berlin.de> wrote in message
> > >
> > > It's a Unix issue.
> > >
> > > Presumably users have /usr/local/bin before /usr/bin on their path,
and
> > > root hasn't. This is as it should be. In fact, it isn't a bad idea
to
> > > keep root's perl separate and not have it hop along with every version
> > > change.
> >
> > Scripts run by users don't execute because there is no longer a Perl
> > executable in /usr/local/bin. In order for me to run the scripts, I need
to
> > be root!
> >
> > It does sound like a Linux path issue and I will pursue that line, but
if
> > you have any add'l thoughts on this, I'd sure like to hear them. Thanks
for
> > your reply.
>
> Make /usr/local/bin/perl a symlink to the perl executable you want the
> users to use.
This is probably the best solution until I figure out what's going on
underneath it all. Thanks for the reply.
------------------------------
Date: Fri, 02 Apr 2004 09:42:37 BST
From: gml4410@ggr.co.uk (Lack Mr G M)
Subject: Re: "which perl": Different for root and users
Message-Id: <2004Apr2.094238@ukwit01>
In article <c4hjaj$h48$2@mamenchi.zrz.TU-Berlin.DE>, anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) writes:
|>
|> Presumably users have /usr/local/bin before /usr/bin on their path, and
|> root hasn't. This is as it should be.
I disagree.
|> In fact, it isn't a bad idea to
|> keep root's perl separate and not have it hop along with every version
|> change.
Well, I'd agree with that, but the same applies to non-root users.
It really depends on what is in /usr/local and who can put things
there. If it is only root-writable then it makes sense for everyone to
have it in their PATH (in the same relative location).
If you can make the root environment as similar as possible to a
normal user environmentthen you will have fewer admin problems.
--
--------- Gordon Lack --------------- gml4410@ggr.co.uk ------------
This message *may* reflect my personal opinion. It is *not* intended
to reflect those of my employer, or anyone else.
------------------------------
Date: 1 Apr 2004 21:15:16 -0800
From: dps2@ix.netcom.com (Peter Steele)
Subject: bash shell script - perl conversion
Message-Id: <5d5c95a1.0404012115.4d2b633e@posting.google.com>
Hello all,
I am trying to teach myself perl and I have a bash shell script which
I
thought might be a good "perl conversion exercise".
My shell script does the following (my apologies if I am boring those
who don't require an explanation ...):
- Set a variable, "INFILE", to be an input file specified as a
commandline
argument.
- For each record in the file "headers" , set a variable ($header) as
the string contained in that record.
- grep the input file INFILE for occurrences of the "$header" string,
and store this result in a variable for further regex processing.
While this is trivial with the shell, I have not yet gotten very far
with perl.
The "headers" file will contain ten lines of text, and the INFILE will
typically be less than 50Kb in size.
Any suggestions?
Thank you all for your time.
Script follows:
....................................................
INFILE=$@
while read header
do
echo "looking for $header in $INFILE"
result=`grep -i $header $INFILE`
done<headers
....................................................
------------------------------
Date: Fri, 02 Apr 2004 07:34:29 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Boxed Perl or ActiveState Perl?
Message-Id: <1l5q60p675kefuc86b8movs2padtdsln7c@4ax.com>
gnari wrote:
>perl is used by many debian administration tools, but I have no idea if
>they would happily use a /usr/local one instead of the debian one.
Dunno about Debian but...
In general, it's considered a bad idea to replace the perl that is used
by the system, by a custom one. Leave it there. If you don't like it
(because it's buggy, unextensible, whatever..) *add* a different
distribution on a different location. You're still free to choose for
your scripts which one to use, by changing the shebang line.
--
Bart.
------------------------------
Date: Fri, 02 Apr 2004 08:02:04 GMT
From: Thomas =?ISO-8859-15?Q?G=F6tz?= <t.goetz@dkfz.de>
Subject: Re: DBI:mysql and huge tables
Message-Id: <069bc.12140783$Id.2030372@news.easynews.com>
ctcgag@hotmail.com wrote:
> Thomas =?ISO-8859-15?Q?G=F6tz?= <t.goetz@dkfz.de> wrote:
>> I'm using a MySQL database with a table that contains around 500.000
>> records. If I now want to select all that rows to do something with them,
>> this is getting _very_ memory-consuming.
>> Here's the code I use:
> ...
>> my $sql = qq{SELECT `SOME_FIELD` ` FROM `SOME_TABLE`};
>> my $sth = $dbh->prepare($sql);
>
> $sth->{mysql_use_result}=1; ## Add this line here
yeah, that is exactly what I was looking for, thanks for that hint! ;-)
As the script is running on a mysql-server that has not too much traffic I
can live with the limitations you mentioned (blocking ...).
Tom
--
Thomas Götz
German Cancer Research Center
------------------------------
Date: Fri, 02 Apr 2004 07:00:43 +0100
From: Henry Law <lawshouse.public@btconnect.com>
Subject: Re: free source for bbs
Message-Id: <0a0q60lurrafl2o97721974kkauobvdj0b@4ax.com>
On Thu, 01 Apr 2004 19:34:31 -0500, Chris Mattern
<matternc@comcast.net> wrote:
>You can't trick me, I know an April Fool's post when
>I see one!
Alas not:
Date: Thu, 1 Apr 2004 12:55:02 -0800
... after mid-day, y'see. Or is that just a British restriction?
Henry Law <>< Manchester, England
------------------------------
Date: Fri, 2 Apr 2004 19:39:57 +0900
From: "CatcherInTheRye" <letnomanenterhere@yahoo.co.kr>
Subject: How do I do when handling the data
Message-Id: <c4jfu3$qf8@netnews.proxy.lucent.com>
Hi, How are you.
I am a complete perl beginner.
So, now I don't know how to handle efficiently the raw data to any data
structure.
89 ;1;148;|89 ;2;316;|89 ;3;484;|45 ;1;142;|
45 ;1;142;|89 ;1;148;|33 ;2;258;| ; ; ;|
89 ;2;316;|89 ;3;484;|101;1;120;| ; ; ;|
89 ;3;484;|89 ;1;148;|89 ;2;316;|46 ;1;76 ;|
46 ;1;76 ;|67 ;2;248;|90 ;3;500;|33 ;2;258;|
33 ;2;258;|46 ;1;76 ;|45 ;1;142;|90 ;3;500;|
90 ;3;500;|91 ;3;372;|33 ;2;258;| ; ; ;|
91 ;3;372;|91 ;1;36 ;|42 ;3;446;|81 ;3;356;|
91 ;1;36 ;|101;1;120;|92 ;1;50 ;| ; ; ;|
92 ;1;50 ;|71 ;1;6 ;|72 ;3;370;|74 ;2;214;|
42 ;3;446;|42 ;1;110;|91 ;3;372;| ; ; ;|
101;1;120;|89 ;2;316;| ; ; ;| ; ; ;|
Raw data shown above.
I hope to check data validation each other data.
Let me show you the meaning of data.
"89 ;1;148" of first line is KEY and means CELL;SECTOR;PN
and has its neighbor list like "89 ;2;316;|89 ;3;484;|45 ;1;142;|"
Other line has same meaning.
I hope to code the script to process following conditions.
1. Don't have same PN in the same line. If there is , print "Same PN in
the '46 ;1;76 ' "
89 ;1;148;|89 ;2;316;|89 ;3;484;|45 ;1;142;|
* * * *
2. Second field "89 ;2;316;" should be existed in the line where "89
;2;316;" is key.
if there is not, print "89 ;1;148;" has "89 ;2;316;" but "89 ;2;316"
don't have "89 ;1;148;".
89 ;1;148;|89 ;2;316;|89 ;3;484;|45 ;1;142;|
+++++++++ *********
89 ;2;316;|89 ;1;149;|89 ;3;484;|101;1;120;|
********* +++++++++
Thanks in advance,
------------------------------
Date: Fri, 02 Apr 2004 12:53:23 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: How do I do when handling the data
Message-Id: <c4jgq2$2jhioi$1@ID-184292.news.uni-berlin.de>
CatcherInTheRye wrote:
> I am a complete perl beginner.
> So, now I don't know how to handle efficiently the raw data to any
> data structure.
<snip>
> I hope to code the script to process following conditions.
<snip>
Then you have a reason to learn how to do it, right?
http://learn.perl.org/
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 02 Apr 2004 07:13:53 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: include different files at run time
Message-Id: <pan.2004.04.02.04.45.11.83400@aursand.no>
On Thu, 01 Apr 2004 09:31:06 -0800, rzhu wrote:
> To support different languages, I'm planning to extract all the text
> strings from the perl CGI code, and define them in different hashes in
> separate file.
There are modules which helps you with this. Take a look at the Locale::*
modules, specifically Locale::Maketext. Be sure to read the documentation
before you dive into it.
--
Tore Aursand <tore@aursand.no>
"Life is pleasant. Death is peaceful. It's the transition that's
troublesome." -- Isaac Asimov
------------------------------
Date: 01 Apr 2004 16:47:24 -0500
From: Uri Guttman <uri.guttman@fmr.com>
Subject: Re: multidimensional hash copy problem
Message-Id: <siscoeqbtloz.fsf@tripoli.fmr.com>
>>>>> "ES" == Eric Schwartz <emschwar@pobox.com> writes:
ES> This is perhaps a tad subtle if you're not clear on how references
ES> work (and to cure that, see perlreftut and perlref). What's going on
ES> here is that $zones{'zone1'} contains a reference to an anonymous hash
ES> which has one key, 'type'. After you assign %zones to %ext_zones,
ES> %ext_zones has a completely different reference to the same anonymous
^^^^^^^^^^^^^^^^^^^^
copy of the same reference
ES> hash. Thus, when you change data in that anonymous hash later, both
ES> %zones and %ext_zones reflect it, because they're both pointing to the
ES> same data.
ES> What you want to do instead is a 'deep copy', which copies not only
ES> the references, but the data they point to. See Randal's article for
actually a deep copy doesn't copy references (or they would have the
same bug as the OP's code has). they create new refs and copy the data
into them.
uri
------------------------------
Date: Thu, 1 Apr 2004 21:15:31 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Need help with a Perl Script Error
Message-Id: <slrnc6pmmj.4m8.tadmc@magna.augustmail.com>
Darren Clark <darren.clark@clarkcompservice.com> wrote:
> The script runs fine when I am using
> IE from a windows machine, but when I use a MAC to call the script, I
> get the following error message:
> # use strict;
It loses all of its utility when you comment it out like that.
> $mypath = '../upload/'.$workorder;
^ ^
^ ^
> # mkdir ($mypath, 0777);
Check the return value to verify that you got what you asked for:
mkdir ($mypath, 0777) or die "could not make '$mypath' $!";
> #Strip directory structure
> $name=~m/^.*(\\|\/)(.*)/; # strip the remote path and keep the
^
^
> # Concatenate the path & file name for UPLOAD
> $myupload = '>'.$mypath.'/'.$newname;
^
^
> I assume it has something to do with how a MAC passess the file
> information that is being uploaded but am not sure if I am right
You are right.
Mac does not use slash as the directory separator.
> or if
> I am how to correct it.
Use the character that a Mac _does_ use as its directory separator. :-)
> I'd appreciate it if someone could give me some direction.
Ask in a Mac newsgroup, or use a module that "knows", such as:
http://search.cpan.org/search?query=Path%3A%3AClass
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 02 Apr 2004 02:22:06 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <gaudne0irqEzv_DdRVn-sw@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: 2 Apr 2004 00:22:00 -0800
From: ken.blau@cox.net (Ken Blau Original Author)
Subject: Re: test
Message-Id: <eb676b53.0404020022.4cbf4b71@posting.google.com>
Tad McClellan <tadmc@augustmail.com> wrote in message news:<slrnc6o7p7.2qk.tadmc@magna.augustmail.com>...
> CatcherInTheRye <letnomanenterhere@yahoo.co.kr> wrote:
>
> > test
>
>
> Please do not abuse our newsgroup. It will annoy people.
>
> We discuss Perl here.
>
> There are other newsgroups for testing news software.
Doth realize I was locked out of my house.
------------------------------
Date: Thu, 1 Apr 2004 21:34:47 -0500
From: "Brian Davis" <brian@knowdotnet.nospam.com>
Subject: Re: Tough (for me) regex case
Message-Id: <ek957sFGEHA.3404@TK2MSFTNGP10.phx.gbl>
You can use the following expression:
"(?<no_quotes>(""|[^"])*)"
Simply access the value of the named group "no_quotes" for each match
returned.
Brian Davis
http://www.knowdotnet.com
"Rob Perkins" <rob_perkins@hotmail.com> wrote in message
news:5sqm60lpp2upam99j9lrmjebjakclh1pod@4ax.com...
> Hello,
>
> I know I'm not a regular, and I'm new to the arcana of regular
> expressions, so I'm a little stuck with two specific cases and I'm
> hoping for a genius:
>
> The case I'm most stumped on is an input string like this:
>
> The "quick" brown "fox jumped ""over"" the" lazy dog.
>
> Where what I want to have matched is the quoted strings, except that
> paired doublequotes don't count, and I don't want to capture the
> quotemarks. In other words, my desired matches are:
>
> <>
> quick
> fox jumped ""over"" the
> </>
>
> If I use: /".+?"/, I get:
>
> <>
> "quick"
> "fox jumped "
> "over"
> " the "
> </>
>
> ...which isn't right. If I use /".+"/, I get:
>
> <>
> "quick" brown "fox jumped ""over"" the"
> </>
>
> ...which also isn't right. So I don't know how to proceed and get the
> match of the strings contained in doublequotes, with the paired
> doublequotes escaped, and the matches without the quotes.
>
> How would you do it?
>
> Rob
------------------------------
Date: 01 Apr 2004 15:52:04 -0500
From: Uri Guttman <uri.guttman@fmr.com>
Subject: Re: uninitialized value in concatenation ...
Message-Id: <sisc7jwzv2tn.fsf@tripoli.fmr.com>
>>>>> "CC" == Chris Conwell <chris@mobiles.co.uk> writes:
>> Are there else-clauses?
CC> 3916 if ($price) {
CC> 3917 if ($price eq "") {
CC> ...
CC> 3920 }
CC> 3921 elsif ($price =~ /TBC/i) {
CC> ...
CC> 3925 }
CC> 3926 elsif ($this_index =~ /INDEXU/) {
CC> ...
CC> 3929 }
CC> 3930 else {
CC> ...
CC> 3935 }
CC> 3936 }
CC> --------------------------------------------------------------------------------
CC> Are you thinking that the error is actually on one of the "elsif"
CC> statements and is being incorrectly flagged as the first "if" line?
that is very possible. perl does sometimes report line numbers in odd
places and this could be one of them. so investigate $this_index's value
but i also asked if the way you generated line numbers are accurate and
handled long lines. you never asnwered that.
uri
------------------------------
Date: Thu, 01 Apr 2004 23:53:51 -0600
From: John Bokma <postmaster@castleamber.com>
Subject: Re: uninitialized value in concatenation ...
Message-Id: <406d007b$0$24338$58c7af7e@news.kabelfoon.nl>
Uri Guttman wrote:
>>>>>>"CC" == Chris Conwell <chris@mobiles.co.uk> writes:
>
>
> >> Are there else-clauses?
> CC> 3916 if ($price) {
> CC> 3917 if ($price eq "") {
> CC> ...
> CC> 3920 }
> CC> 3921 elsif ($price =~ /TBC/i) {
> CC> ...
> CC> 3925 }
> CC> 3926 elsif ($this_index =~ /INDEXU/) {
> CC> ...
> CC> 3929 }
> CC> 3930 else {
> CC> ...
> CC> 3935 }
> CC> 3936 }
>
> CC> --------------------------------------------------------------------------------
>
> CC> Are you thinking that the error is actually on one of the "elsif"
> CC> statements and is being incorrectly flagged as the first "if" line?
>
> that is very possible. perl does sometimes report line numbers in odd
> places and this could be one of them. so investigate $this_index's value
I remember this being a bug (got bitten by it a few times about a year
ago), and it is indeed elsif related. Couldn´t find it with Google though.
--
John personal page: http://johnbokma.com/
Freelance Perl / Java developer available - http://castleamber.com/
------------------------------
Date: Fri, 02 Apr 2004 03:23:08 GMT
From: perl coder <perlcdr@mail.rumania>
Subject: Win32::FileSecurity doesn't show all perms?
Message-Id: <w05bc.3736$b_5.2262@bignews5.bellsouth.net>
I'm trying to use Win32::FileSecurity to view file permissions on a
Windows XP machine. Here's my code:
use Win32::FileSecurity;
use Data::Dumper;
$file = shift @ARGV or die "Usage: $0 <filename>\n";
%perms = ();
Win32::FileSecurity::Get($file, \%perms) or die $!;
print "NTFS DACLS:\n";
print Dumper(\%perms);
foreach $user (keys %perms) {
@rights = ();
Win32::FileSecurity::EnumerateRights($perms{$user}, \@rights);
print " *** $user : ", join(' ', @rights), "\n";
}
The script runs without errors, but it only shows permissions for 3
users. It doesn't show any perms for 'Everyone' and 'Power Users'. I
have no idea why... Here's some sample output:
NTFS DACLS:
$VAR1 = {
'BUILTIN\\Administrators' => 2032127,
'NT AUTHORITY\\SYSTEM' => 2032127,
'CRASHME\\mm' => 2032127
};
*** BUILTIN\Administrators : DELETE READ_CONTROL WRITE_DAC WRITE_OWNER
SYNCHRONIZE STANDARD_RIGHTS_REQUIRED STANDARD_RIGHTS_READ
STANDARD_RIGHTS_WRITE STANDARD_RIGHTS_EXECUTE STANDARD_RIGHTS_ALL
READ CHANGE ADD FULL
*** NT AUTHORITY\SYSTEM : DELETE READ_CONTROL WRITE_DAC WRITE_OWNER
SYNCHRONIZE STANDARD_RIGHTS_REQUIRED STANDARD_RIGHTS_READ
STANDARD_RIGHTS_WRITE STANDARD_RIGHTS_EXECUTE STANDARD_RIGHTS_ALL READ
CHANGE ADD FULL
*** CRASHME\mm : DELETE READ_CONTROL WRITE_DAC WRITE_OWNER SYNCHRONIZE
STANDARD_RIGHTS_REQUIRED STANDARD_RIGHTS_READ STANDARD_RIGHTS_WRITE
STANDARD_RIGHTS_EXECUTE STANDARD_RIGHTS_ALL READ CHANGE ADD FULL
Ultimately I want to use this code to find out if a given user has read
access to a given file. For instance, I may wish to know if user 'fred'
can read the file "C:\Documents and Settings\joe\my_precious.txt", and
with the above code I won't be able to know because 'fred' would fall in
the 'Everyone' group, which isn't listed. :-(
Oh, one last question, while I'm on a roll. ;-) I'm very new to the
Windows world, and have almost zero understanding of the ACL system.
I've tried reading various docs and googling around but haven't found
much good info. But what I understand so far is that if someone has
READ access to a file, they can view the data inside. Is this correct?
Or do they also need GENERIC_READ access as well?
--
No crazy stuff in my email. ;-)
------------------------------
Date: Thu, 01 Apr 2004 22:12:45 -0700
From: Bill <wherrera@lynxview.com>
Subject: Re: Win32::FileSecurity doesn't show all perms?
Message-Id: <WbSdnXBsvYXDa_Hd4p2dnA@adelphia.com>
perl coder wrote:
> I'm trying to use Win32::FileSecurity to view file permissions on a
> Windows XP machine. Here's my code:
>
> use Win32::FileSecurity;
> use Data::Dumper;
>
> $file = shift @ARGV or die "Usage: $0 <filename>\n";
>
> %perms = ();
> Win32::FileSecurity::Get($file, \%perms) or die $!;
> print "NTFS DACLS:\n";
> print Dumper(\%perms);
> foreach $user (keys %perms) {
> @rights = ();
> Win32::FileSecurity::EnumerateRights($perms{$user}, \@rights);
> print " *** $user : ", join(' ', @rights), "\n";
> }
>
> The script runs without errors, but it only shows permissions for 3
> users. It doesn't show any perms for 'Everyone' and 'Power Users'. I
> have no idea why... Here's some sample output:
>
> NTFS DACLS:
> $VAR1 = {
> 'BUILTIN\\Administrators' => 2032127,
> 'NT AUTHORITY\\SYSTEM' => 2032127,
> 'CRASHME\\mm' => 2032127
> };
> *** BUILTIN\Administrators : DELETE READ_CONTROL WRITE_DAC WRITE_OWNER
> SYNCHRONIZE STANDARD_RIGHTS_REQUIRED STANDARD_RIGHTS_READ
> STANDARD_RIGHTS_WRITE STANDARD_RIGHTS_EXECUTE STANDARD_RIGHTS_ALL
> READ CHANGE ADD FULL
> *** NT AUTHORITY\SYSTEM : DELETE READ_CONTROL WRITE_DAC WRITE_OWNER
> SYNCHRONIZE STANDARD_RIGHTS_REQUIRED STANDARD_RIGHTS_READ
> STANDARD_RIGHTS_WRITE STANDARD_RIGHTS_EXECUTE STANDARD_RIGHTS_ALL READ
> CHANGE ADD FULL
> *** CRASHME\mm : DELETE READ_CONTROL WRITE_DAC WRITE_OWNER SYNCHRONIZE
> STANDARD_RIGHTS_REQUIRED STANDARD_RIGHTS_READ STANDARD_RIGHTS_WRITE
> STANDARD_RIGHTS_EXECUTE STANDARD_RIGHTS_ALL READ CHANGE ADD FULL
>
> Ultimately I want to use this code to find out if a given user has read
> access to a given file. For instance, I may wish to know if user 'fred'
> can read the file "C:\Documents and Settings\joe\my_precious.txt", and
> with the above code I won't be able to know because 'fred' would fall in
> the 'Everyone' group, which isn't listed. :-(
>
> Oh, one last question, while I'm on a roll. ;-) I'm very new to the
> Windows world, and have almost zero understanding of the ACL system.
> I've tried reading various docs and googling around but haven't found
> much good info. But what I understand so far is that if someone has
> READ access to a file, they can view the data inside. Is this correct?
> Or do they also need GENERIC_READ access as well?
>
>
GENERIC_READ is just the logical or mask of all the Win32 read
permissions types, sort of :).
see this:
http://www.develop.com/kbrown/book/html/whatis_permission.html
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 6355
***************************************
