[31048] in Perl-Users-Digest
Perl-Users Digest, Issue: 2293 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 24 09:09:42 2009
Date: Tue, 24 Mar 2009 06:09:08 -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 Tue, 24 Mar 2009 Volume: 11 Number: 2293
Today's topics:
Re: i have a question <justin.0903@purestblue.com>
new CPAN modules on Tue Mar 24 2009 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Read File and Output to new format <Ansher.M@gmail.com>
Re: regex question: extended [^...] concept? <nospam-abuse@ilyaz.org>
Re: regex question: extended [^...] concept? <ben@morrow.me.uk>
Re: regex question: extended [^...] concept? sln@netherlands.com
Re: regex question: extended [^...] concept? <whynot@pozharski.name>
regex that ever fail (was: regex question: extended [^. <whynot@pozharski.name>
Send Data to Another File. <sitawit@gmail.com>
Re: Send Data to Another File. <RedGrittyBrick@spamweary.invalid>
Re: Send Data to Another File. <jurgenex@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 24 Mar 2009 09:37:39 -0000
From: Justin C <justin.0903@purestblue.com>
Subject: Re: i have a question
Message-Id: <263e.49c8a9e3.e02b1@zem>
On 2009-03-23, Ben Morrow <ben@morrow.me.uk> wrote:
>
> Quoth Tad J McClellan <tadmc@seesig.invalid>:
>>
>> You should use single quotes unless you need one of the two extra
>> things that double quotes gives you.
>
> I used to think that, until http://markmail.org/message/e4i3ngej24an7uch
> convinced me otherwise. The section on double-quoting starts about a
> third of the way down (search for 'politically-correct Bowdlerization').
Makes a strong argument!
Justin.
--
Justin C, by the sea.
------------------------------
Date: Tue, 24 Mar 2009 04:42:28 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Mar 24 2009
Message-Id: <KGzuEs.15zt@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
AI-Genetic-Pro-0.341
http://search.cpan.org/~strzelec/AI-Genetic-Pro-0.341/
Efficient genetic algorithms for professional purpose.
----
Acme-Grep2D-0.01
http://search.cpan.org/~thecramps/Acme-Grep2D-0.01/
Grep in 2 dimensions
----
App-SocialSKK-0.02
http://search.cpan.org/~kentaro/App-SocialSKK-0.02/
SKK Goes Social
----
Async-Hooks-0.05
http://search.cpan.org/~melo/Async-Hooks-0.05/
Hook system with asynchronous capabilities
----
Attribute-Generator-0.02
http://search.cpan.org/~rintaro/Attribute-Generator-0.02/
Python like generator powered by Coro
----
CGI-Application-Dispatch-2.16
http://search.cpan.org/~markstos/CGI-Application-Dispatch-2.16/
Dispatch requests to CGI::Application based objects
----
CPANPLUS-Dist-Arch-0.04
http://search.cpan.org/~juster/CPANPLUS-Dist-Arch-0.04/
CPANPLUS backend for building Archlinux pacman packages
----
Catalyst-Controller-SOAP-1.11
http://search.cpan.org/~druoso/Catalyst-Controller-SOAP-1.11/
Catalyst SOAP Controller
----
DBD-ADO-2.97
http://search.cpan.org/~sgoeldner/DBD-ADO-2.97/
A DBI driver for Microsoft ADO (Active Data Objects)
----
Data-Dump-Streamer-2.09
http://search.cpan.org/~yves/Data-Dump-Streamer-2.09/
Accurately serialize a data structure as Perl code.
----
Data-FormValidator-Filters-Image-0.40
http://search.cpan.org/~ceeshek/Data-FormValidator-Filters-Image-0.40/
Filter that allows you to shrink incoming image uploads using Data::FormValidator
----
DateTime-TimeZone-0.86
http://search.cpan.org/~drolsky/DateTime-TimeZone-0.86/
Time zone object base class and factory
----
EAFDSS-0.20
http://search.cpan.org/~hasiotis/EAFDSS-0.20/
Electronic Fiscal Signature Devices Library
----
Email-Valid-0.181
http://search.cpan.org/~rjbs/Email-Valid-0.181/
Check validity of Internet email addresses
----
Fey-0.23
http://search.cpan.org/~drolsky/Fey-0.23/
Better SQL Generation Through Perl
----
Fey-ORM-0.22
http://search.cpan.org/~drolsky/Fey-ORM-0.22/
A Fey-based ORM
----
File-Lock-Multi-0.05
http://search.cpan.org/~crakrjack/File-Lock-Multi-0.05/
Lock files more than once
----
Inline-Rakudo-0.01
http://search.cpan.org/~szabgab/Inline-Rakudo-0.01/
allow to use Rakudo from Perl 5 code
----
Kx-0.039
http://search.cpan.org/~markpf/Kx-0.039/
Perl extension for Kdb+ http://kx.com
----
Math-Cartesian-Product-1.003
http://search.cpan.org/~prbrenan/Math-Cartesian-Product-1.003/
Generate the cartesian product of zero or more lists.
----
Math-Disarrange-List-1.004
http://search.cpan.org/~prbrenan/Math-Disarrange-List-1.004/
Generate all disarrangements of a list.
----
Math-Permute-List-1.004
http://search.cpan.org/~prbrenan/Math-Permute-List-1.004/
Generate all permutations of a list.
----
Math-Subsets-List-1.004
http://search.cpan.org/~prbrenan/Math-Subsets-List-1.004/
----
Math-Transform-List-1.004
http://search.cpan.org/~prbrenan/Math-Transform-List-1.004/
Generate specified transformations of a list.
----
Net-FTPSSL-0.08
http://search.cpan.org/~cleach/Net-FTPSSL-0.08/
A FTP over SSL/TLS class
----
OpenOffice-UNO-0.06
http://search.cpan.org/~mbarbon/OpenOffice-UNO-0.06/
interface to OpenOffice's UNO runtime
----
PDF-Create-1.03
http://search.cpan.org/~markusb/PDF-Create-1.03/
create PDF files
----
Perl-Dist-WiX-v0.160
http://search.cpan.org/~csjewell/Perl-Dist-WiX-v0.160/
Experimental 4th generation Win32 Perl distribution builder
----
WWW-Contact-0.21
http://search.cpan.org/~fayland/WWW-Contact-0.21/
Get contacts/addressbook from Web
----
WWW-YahooJapan-KanaAddress-0.1.4_2
http://search.cpan.org/~hiratara/WWW-YahooJapan-KanaAddress-0.1.4_2/
translating the address in Japan into kana.
----
Workflow-1.33_2
http://search.cpan.org/~jonasbn/Workflow-1.33_2/
Simple, flexible system to implement workflows
----
XML-Tiny-2.01
http://search.cpan.org/~dcantrell/XML-Tiny-2.01/
simple lightweight parser for a subset of XML
----
parrot-1.0.0
http://search.cpan.org/~arandal/parrot-1.0.0/
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Tue, 24 Mar 2009 07:10:42 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <SH%xl.16611$as4.513@nlpi069.nbdc.sbc.com>
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.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Tue, 24 Mar 2009 06:07:16 -0700 (PDT)
From: ansher <Ansher.M@gmail.com>
Subject: Read File and Output to new format
Message-Id: <379d94cf-01e0-4ea2-aa86-ddf75487946b@o11g2000yql.googlegroups.com>
Hello
What I am trying to achieve is to read a file and write the formatted
text into a new file. But I am facing some difficulty with that
Format: I am reading a file where line continuation is indicated by
=93+=94 sign at the beginning of the new line. Remove the line
continuation and add (join) this new line to prev. one
NOTE: file do not have line number, it is only for your reference.
Line13: n01contacts/friends do you
Line14: +have in each of the services ;c=3Dcontacts(433)=921=92
Output: n01 contacts/friends do you have in each of the
services ;c=3Dcontacts(433)=921=92
Challenges: I cannot always consider =93+=94sign as the beginning of the
new line, those instances are
1.Section of lines should not be formatted after text =91fld=92, refer
line 16-23 should not be formatted. Lines after this section must be
formatted.
2. Section of lines should not be formatted after text =91val=92, refer
line 29-33 should not be formatted. Lines after this section must be
formatted.
3. Refer line 9-12, line 10 ends with ; but lines 11 & 12 do not.
After formatting line should be separated by single ;
*include q10.qin;txt=3DUNIQUENESS; bb=3DTop line; tx=3DMid Value;tb=3DL=
ow
Value
4.Refer line 13-14,
Line13: n01contacts/friends do you
Line14: +have in each of the services ;c=3Dcontacts(433)=921=92
After formatting line should not be separated by single ; instead it
should read as
n01contacts/friends do you have in each of the services ;c=3Dcontacts
(433)=921=92
Any solution to this will be of great help to me. Thanks
Format of original file:
Line1: n010-10 ;c=3Dtemp(433)'1'
Line2: n0111-25 ;c=3Dtemp(433)'2'
Line3: n0126-50 ;c=3Dtemp(433)'3'
Line4: n0151-100 ;c=3Dtemp(433)'4'
Line5: n01101-150 ;c=3Dtemp(433)'5'
Line6: net1151 CONTACTS OR MORE (NET)
Line7: n01151-200 ;c=3Dtemp(433)'6'
Line8: n01200+ ;c=3Dtemp(433)'7'
Line9: *include q10.qin;txt=3DUNIQUENESS
Line10: +bb=3DTop line;
Line11: +tx=3DMid Value
Line12: +tb=3DLow Value
Line13: n01contacts/friends do you
Line14: +have in each of the services ;c=3Dcontacts(433)=921=92
Line15: net1CONVENIENCE (NET)
Line16: fld c(m00),c(m96):3
Line17: +Easy to find/noticeable=3D044
Line18: +Quick=3D045
Line19: +Convenient=3D046
Line20: +Other convenience comments=3D050;%nosort
Line21: netend1
Line22: fld c(m00),c(m96):3
Line23: +NA=3D996;%nosort
Line24: *include lib\9pscale.qin;col(a)=3D697
Line25: +txt1=3DValue 1
Line26: +txt2=3D
Line27: +txt3=3D
Line28: +txt4=3DValue 4
Line29: val c(650,652);i
Line30: +1-25=3D1-25
Line31: +26-50=3D26-50
Line32: +51-75=3D51-75
Line33: +76-100=3D76-100
Line34: n01Clear testing/QA
Line35: +requirements ;c=3Dc100'1'
Expected outputs after formatting:
n010-10 ;c=3Dtemp(433)'1'
n0111-25 ;c=3Dtemp(433)'2'
n0126-50 ;c=3Dtemp(433)'3'
n0151-100 ;c=3Dtemp(433)'4'
n01101-150 ;c=3Dtemp(433)'5'
net1151 CONTACTS OR MORE (NET)
n01151-200 ;c=3Dtemp(433)'6'
n01200+ ;c=3Dtemp(433)'7'
*include q10.qin;txt=3DUNIQUENESS;bb=3DTop line;tx=3DMid Value;tb=3DLow Val=
ue
n01 contacts/friends do you have in each of the services ;c=3Dcontacts
(433)=921=92
net1CONVENIENCE (NET)
fld c(m00),c(m96):3
+Easy to find/noticeable=3D044
+Quick=3D045
+Convenient=3D046
+Other convenience comments=3D050;
netend1
fld c(m00),c(m96):3
+NA=3D996;%nosort
*include lib\9pscale.qin;col(a)=3D697;txt1=3DValue
1;txt2=3D;txt3=3D;txt4=3DValue 4
val c(650,652);i
+1-25=3D1-25
+26-50=3D26-50
+51-75=3D51-75
+76-100=3D76-100
n01Clear testing/QA
requirements ;=
c=3Dc100'1'
------------------------------
Date: Tue, 24 Mar 2009 01:27:46 GMT
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: regex question: extended [^...] concept?
Message-Id: <slrngsgdoi.sp8.nospam-abuse@chorin.math.berkeley.edu>
On 2009-03-23, Werner Lemberg <wl@gnu.org> wrote:
> foo ... foo ... bar
>
> where `...' doesn't contain the word `foo'. How can I write a regular
> expression which matches `foo ... bar' but not `foo ... foo ... bar'?
This does not make sense, since `foo ... bar' is a substring of `foo
... foo ... bar'.
I assume you want to allow the REX to match this substring, but not
the larger string. Then the simplest solution would be to fasttrack to
the LATEST occurence of foo which is followed by bar:
/^ (?> .* (?=foo .* bar) ) (foo .* bar) /x; # add \b where needed
or just (depending on the needs)
/ ^ .* (foo .* bar) /x;
If you want to disallow ANY match which contains foo foo bar, then it
may as simple as
/ ^ (?! .*? foo .* foo .* bar) .*? ( foo .* bar )/x
or
/ ^ (?! (?> (?> .*? foo) .*? foo) .* bar) .*? ( foo .* bar )/x
However, the problem becomes much trickier if you prohibit using ^...
Hope this helps,
Ilya
P.S. Of course, with "onion rings" implemented (google for it) there
would be no problem whatsoever...
------------------------------
Date: Tue, 24 Mar 2009 01:57:32 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: regex question: extended [^...] concept?
Message-Id: <c9rl96-n2j.ln1@osiris.mauzo.dyndns.org>
Quoth Werner Lemberg <wl@gnu.org>:
> Ben Morrow <ben@morrow.me.uk> wrote:
>
> > /foo (?: (?! fob (?!ar) ) . )* bar/x
>
> Uuh, a negative lookahead *within* another negative lookahead. How is the
> exactly defined? Is it equivalent to
>
> (?! fob ) (?! ar )
No, not in the least. For instance, "fobo" matches /^(?!fob(?!ar))/ but
doesn't match /^(?!fob)(?!ar)/.
It may help you to think of
(?!pattern)
as being something like
(?{ if (/pattern/) { fail } })
where 'fail' is a hypothetical builtin that causes the surrounding match
to fail. (Of course $_ would have to have the appropriate value, as
well, which it doesn't.) OTOH, it may not... :)
In other words, (?!) starts a fresh instance of the regex engine with a
new pattern, tries the match at the current offset, and fails if this
sub-match succeeds. A nested (?! (?!) ) ends up with a third layer of
nesting, whereas (?!)(?!) only ever has two layers. It's similar to the
difference between
if () {
unless () {
unless () {
}
}
}
and
if () {
unless () {
}
unless () {
}
}
I did say the pattern was confusing: if you're only just getting used to
the idea of lookaround assertions, it's probably best not to worry about
the possibility of nesting them just yet :).
Ben
------------------------------
Date: Tue, 24 Mar 2009 03:03:22 GMT
From: sln@netherlands.com
Subject: Re: regex question: extended [^...] concept?
Message-Id: <79jgs4p56gqj9peuk83crui5e3ao8cahhu@4ax.com>
On Mon, 23 Mar 2009 20:00:29 +0000 (UTC), Werner Lemberg <wl@gnu.org> wrote:
>
>Folks,
>
>
>consider this input:
>
> foo ... foo ... bar
>
>where `...' doesn't contain the word `foo'. How can I write a regular
>expression which matches `foo ... bar' but not `foo ... foo ... bar'? Were
>it a single character as in
>
> f ... f ... bar
>
>I could write
>
> /f[^f]*bar/
>
>but how can I do something similar for a word? In other words, I search an
>extension of the [^.] concept which covers a sequence of characters.
>
>I've looked into both the `perlre' and `perlretut' manual pages (of perl
>5.10.0), but it contains relevant to this problem.
>
>
> Werner
I've always thought these are good ways.
-sln
---------------------------------------
use strict;
use warnings;
if ( "foo ... foo ... bar ... bar" =~ /(foo (?: . (?! foo) ) * bar)/x )
{
print "$1\n";
}
## or
if ( "foo ... foo ... bar ... bar" =~ /(foo (?: . (?! foo) ) *? bar)/x )
{
print "$1\n";
}
__END__
foo ... bar ... bar
foo ... bar
------------------------------
Date: Tue, 24 Mar 2009 10:26:26 +0200
From: Eric Pozharski <whynot@pozharski.name>
Subject: Re: regex question: extended [^...] concept?
Message-Id: <slrngsh6ac.6ve.whynot@orphan.zombinet>
On 2009-03-23, Werner Lemberg <wl@gnu.org> wrote:
*SKIP*
> Thanks for the answers. I'm really surprised that there are so many regex
> extensions in Perl but not a single one which covers this. Is this
> difficult to handle in a regex machine, or is there no need normally for
> it?
Watch what you say. Those aren't 'regex extensions in Perl'. Those are
Perl regex (or 'perlre', for short)
*CUT*
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
Date: Tue, 24 Mar 2009 10:50:35 +0200
From: Eric Pozharski <whynot@pozharski.name>
Subject: regex that ever fail (was: regex question: extended [^...] concept?)
Message-Id: <slrngsh7nm.6ve.whynot@orphan.zombinet>
On 2009-03-24, Ben Morrow <ben@morrow.me.uk> wrote:
*SKIP*
> as being something like
>
> (?{ if (/pattern/) { fail } })
>
> where 'fail' is a hypothetical builtin that causes the surrounding match
> to fail. (Of course $_ would have to have the appropriate value, as
> well, which it doesn't.) OTOH, it may not... :)
Once I've considered aproach of intentionally failing match within
perlre itself (prepropcessing wasn't an option).
I would come with something like this:
perl -Mstrict -wle '
my $x = qr[(??{ substr($`, -1, 1) eq q|f| ? qr/(?<=f)/ : qr/(?!.|$)/
})];
foreach ( q||, qw| x f fx xf | ) {
print m{$x};
print qq|<$&>|;
print qq|$_\n|; };
print q|FIN|'
Use of uninitialized value $& in concatenation (.) or string at -e line 5.
<>
Use of uninitialized value $& in concatenation (.) or string at -e line 5.
<>
x
1
<>
f
1
<>
fx
1
<>
xf
FIN
But isn't that a way havy (I'm not even about C<$`>)?
*CUT*
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
Date: Mon, 23 Mar 2009 23:16:38 -0700 (PDT)
From: ZYP <sitawit@gmail.com>
Subject: Send Data to Another File.
Message-Id: <d4b49dd3-a9ef-4750-8220-c576c568276c@k19g2000prh.googlegroups.com>
Hi,
I'm new here and actually I don't understand perl much.
My problem is how to send data to another perl file.
- The sender is perl too. It contain data in Hash and some Parameter.
- The receiver is perl. And It need to collect both of Hash and
Parameter from the sender.
Can someone guide me for perl script how to send/receive with perl
while the data is in Hash and some Parameter.
Thank you very much.
ZYP
------------------------------
Date: Tue, 24 Mar 2009 09:59:24 +0000
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: Send Data to Another File.
Message-Id: <49c8af06$0$2518$da0feed9@news.zen.co.uk>
ZYP wrote:
> My problem is how to send data to another perl file.
You might want to send data to another running Perl program.
> - The sender is perl too. It contain data in Hash and some Parameter.
> - The receiver is perl. And It need to collect both of Hash and
> Parameter from the sender.
>
> Can someone guide me for perl script how to send/receive with perl
> while the data is in Hash and some Parameter.
There must be many ways. One way would be to use SOAP::Lite.
If the two perl scripts are not running concurrently and separately then
you might consider simply making modules of one that can be used by
the other.
perldoc perlipc
search.cpan.org will find you solutions such as Data::Serializer
--
RGB
------------------------------
Date: Tue, 24 Mar 2009 04:38:03 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Send Data to Another File.
Message-Id: <4rghs418veh78nrhdg76766m9nntdv6pu1@4ax.com>
ZYP <sitawit@gmail.com> wrote:
>I'm new here and actually I don't understand perl much.
>My problem is how to send data to another perl file.
To send data to a file you simply open() that file and then print() to
the file handle that is associated with that file. There are several
different options which allow you to write from the beginning, append,
position the write pointer, read/write etc. .
>- The sender is perl too. It contain data in Hash and some Parameter.
>- The receiver is perl. And It need to collect both of Hash and
>Parameter from the sender.
Let me guess: you are not talking about writing data to a file but about
transmitting data between two Perl programs, i.e. two Perl processes?
>Can someone guide me for perl script how to send/receive with perl
>while the data is in Hash and some Parameter.
There are numerous options. On CPAN you can find modules for pretty much
any common IPC (Inter Process Communication) method that has ever been
invented.
jue
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2293
***************************************
