[31343] in Perl-Users-Digest
Perl-Users Digest, Issue: 2588 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Sep 8 06:09:44 2009
Date: Tue, 8 Sep 2009 03: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, 8 Sep 2009 Volume: 11 Number: 2588
Today's topics:
Re: Another way of resizing an Image? <justin.0908@purestblue.com>
Re: Cookies [Firefox/IE] <wassupme@gmail.com>
Re: Cookies [Firefox/IE] <uri@StemSystems.com>
FAQ 2.14 Where are the archives for comp.lang.perl.misc <brian@theperlreview.com>
FAQ 4.31 How can I split a [character] delimited string <brian@theperlreview.com>
IPC::Open2::open2() -- How to pass strings stdin, stdou <jerrykrinock@gmail.com>
Re: IPC::Open2::open2() -- How to pass strings stdin, s <uri@StemSystems.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: replace words <uri@StemSystems.com>
Re: replace words <nat.k@gm.ml>
Re: replace words <uri@StemSystems.com>
Re: Why does "$v = @ARGV[0]" work ? <nat.k@gm.ml>
Re: Why does "$v = @ARGV[0]" work ? <uri@StemSystems.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 08 Sep 2009 09:15:29 -0000
From: Justin C <justin.0908@purestblue.com>
Subject: Re: Another way of resizing an Image?
Message-Id: <422e.4aa620b1.81548@zem>
On 2009-09-05, ccc31807 <cartercc@gmail.com> wrote:
> I'm starting a project (a web app) that will require thumbnails of a
> fairly large number of JPGs that are already accessible over a web
> server.
>
> Would it be better to write a script to make all the thumbnails at
> once and store them in the database along with the full size pics?
>
> Or would it be better to create the thumbnail dynamically when it's
> requested? We don't anticipate much traffic for this.
Personally I don't like storing binary data in a database, I much prefer
storing a link to it.
WRT re-sizing on-the-fly, this is going to be slower than just serving
the image to the browser, but it might not be much. How are you doing
for space on the server? Is having thumbnails for all images going to
take up too much room? If so then thumbnails on-the-fly would be better.
When I had the need to have about 3000 images, plus thumb-nails, I
didn't have space concerns so I created the thumb-nails before
up-loading.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Mon, 7 Sep 2009 18:24:47 -0700 (PDT)
From: wassup <wassupme@gmail.com>
Subject: Re: Cookies [Firefox/IE]
Message-Id: <dee2738e-1b54-40ba-9fa0-c252e6fad7e6@y9g2000yqn.googlegroups.com>
this one doesnt seem to output any erros, but i still cant use the
page... what is wrong here?
#!/usr/bin/perl
use strict;
use warnings;
use WWW::Mechanize;
use HTTP::Cookies;
my $cookie_jar = HTTP::Cookies::Netscape->new(file => "/root/.netscape/
navigator/bbj1xsox.default/cookies.txt",autosave => 1,);
my $m = WWW::Mechanize->new( cookie_jar=> $cookie_jar);
$m->get("http://www.whateverpage.com/test.php");
etc
etc
...
------------------------------
Date: Mon, 07 Sep 2009 23:42:29 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Cookies [Firefox/IE]
Message-Id: <87fxayp0ey.fsf@quad.sysarch.com>
>>>>> "w" == wassup <wassupme@gmail.com> writes:
w> this one doesnt seem to output any erros, but i still cant use the
w> page... what is wrong here?
w> #!/usr/bin/perl
w> use strict;
w> use warnings;
w> use WWW::Mechanize;
w> use HTTP::Cookies;
w> my $cookie_jar = HTTP::Cookies::Netscape->new(file => "/root/.netscape/
w> navigator/bbj1xsox.default/cookies.txt",autosave => 1,);
w> my $m = WWW::Mechanize->new( cookie_jar=> $cookie_jar);
w> $m->get("http://www.whateverpage.com/test.php");
it is likely that you need the cookie that comes from logging in to the
page itself. if you use an old cookie from a previous login it may not
work because the site timed out the session. so you have to login fresh
with the user/password in the auth part of the request.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 08 Sep 2009 10:00:02 GMT
From: PerlFAQ Server <brian@theperlreview.com>
Subject: FAQ 2.14 Where are the archives for comp.lang.perl.misc?
Message-Id: <CWppm.22952$4t6.16280@newsfe06.iad>
This is an excerpt from the latest version perlfaq2.pod, which
comes with the standard Perl distribution. These postings aim to
reduce the number of repeated questions as well as allow the community
to review and update the answers. The latest version of the complete
perlfaq is at http://faq.perl.org .
--------------------------------------------------------------------
2.14: Where are the archives for comp.lang.perl.misc?
The Google search engine now carries archived and searchable newsgroup
content.
http://groups.google.com/group/comp.lang.perl.misc/topics
If you have a question, you can be sure someone has already asked the
same question at some point on c.l.p.m. It requires some time and
patience to sift through all the content but often you will find the
answer you seek.
--------------------------------------------------------------------
The perlfaq-workers, a group of volunteers, maintain the perlfaq. They
are not necessarily experts in every domain where Perl might show up,
so please include as much information as possible and relevant in any
corrections. The perlfaq-workers also don't have access to every
operating system or platform, so please include relevant details for
corrections to examples that do not work on particular platforms.
Working code is greatly appreciated.
If you'd like to help maintain the perlfaq, see the details in
perlfaq.pod.
------------------------------
Date: Tue, 08 Sep 2009 04:00:04 GMT
From: PerlFAQ Server <brian@theperlreview.com>
Subject: FAQ 4.31 How can I split a [character] delimited string except when inside [character]?
Message-Id: <8Fkpm.408543$Ta5.36039@newsfe15.iad>
This is an excerpt from the latest version perlfaq4.pod, which
comes with the standard Perl distribution. These postings aim to
reduce the number of repeated questions as well as allow the community
to review and update the answers. The latest version of the complete
perlfaq is at http://faq.perl.org .
--------------------------------------------------------------------
4.31: How can I split a [character] delimited string except when inside [character]?
Several modules can handle this sort of parsing--"Text::Balanced",
"Text::CSV", "Text::CSV_XS", and "Text::ParseWords", among others.
Take the example case of trying to split a string that is
comma-separated into its different fields. You can't use "split(/,/)"
because you shouldn't split if the comma is inside quotes. For example,
take a data line like this:
SAR001,"","Cimetrix, Inc","Bob Smith","CAM",N,8,1,0,7,"Error, Core Dumped"
Due to the restriction of the quotes, this is a fairly complex problem.
Thankfully, we have Jeffrey Friedl, author of *Mastering Regular
Expressions*, to handle these for us. He suggests (assuming your string
is contained in $text):
@new = ();
push(@new, $+) while $text =~ m{
"([^\"\\]*(?:\\.[^\"\\]*)*)",? # groups the phrase inside the quotes
| ([^,]+),?
| ,
}gx;
push(@new, undef) if substr($text,-1,1) eq ',';
If you want to represent quotation marks inside a
quotation-mark-delimited field, escape them with backslashes (eg, "like
\"this\"".
Alternatively, the "Text::ParseWords" module (part of the standard Perl
distribution) lets you say:
use Text::ParseWords;
@new = quotewords(",", 0, $text);
--------------------------------------------------------------------
The perlfaq-workers, a group of volunteers, maintain the perlfaq. They
are not necessarily experts in every domain where Perl might show up,
so please include as much information as possible and relevant in any
corrections. The perlfaq-workers also don't have access to every
operating system or platform, so please include relevant details for
corrections to examples that do not work on particular platforms.
Working code is greatly appreciated.
If you'd like to help maintain the perlfaq, see the details in
perlfaq.pod.
------------------------------
Date: Mon, 7 Sep 2009 21:52:49 -0700 (PDT)
From: Jerry Krinock <jerrykrinock@gmail.com>
Subject: IPC::Open2::open2() -- How to pass strings stdin, stdout?
Message-Id: <023c6516-9394-4f2b-8827-59f6477e8f9d@v15g2000prn.googlegroups.com>
Markdown.pl is a Perl text-processing filter which takes input from
stdin and outputs to stdout. I'd like to call it as a child process
from within my script -- pass it a string and get a string back. I've
come to believe that this requires something like IPC::Open2:open2()
and have written the following code. However, the child process never
exits, as though maybe it's waiting for the stdin pipe to close.
What's wrong with this code?...
#!/usr/bin/perl
require IPC::Open2 ;
use strict ;
my $markdownIn = "*Hello* **World**\n" ;
print ("markdownIn = $markdownIn") ;
my $cmd = '/Users/jk/Downloads/Markdown_1.0.1/Markdown.pl';
my $markdownOut ;
my $childpid = IPC::Open2::open2($markdownOut, $markdownIn, $cmd)
or die "can't open pipe to $cmd: $!";
waitpid( $childpid, 0 );
my $cmdExitStatus = $? >> 8;
print ("cmdExitStatus = $cmdExitStatus\n") ;
print ("markdownOut = $markdownOut\n") ;
If I comment out the waitpid(), then it runs but does not give the
desired result:
markdownIn = *Hello* **World**
cmdExitStatus = 0
markdownOut = GLOB(0x816b3c)
Markdown.pl definitely works fine if I give it that string from stdin
in a bash shell:
Jerrys-Mac-Mini:~ jk$ echo "*Hello* **World**\n" | /Users/jk/Downloads/
Markdown_1.0.1/Markdown.pl
<p><em>Hello</em> <strong>World</strong>\n</p>
Thank you!
Jerry Krinock
------------------------------
Date: Tue, 08 Sep 2009 01:21:41 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: IPC::Open2::open2() -- How to pass strings stdin, stdout?
Message-Id: <87y6oqm2oq.fsf@quad.sysarch.com>
>>>>> "JK" == Jerry Krinock <jerrykrinock@gmail.com> writes:
JK> require IPC::Open2 ;
generally 'use' is best for loading modules. require works but it is a
runtime thing vs compile time for use. also by using use you will get
the open2 sub imported into your namespace.
JK> use strict ;
JK> my $markdownIn = "*Hello* **World**\n" ;
JK> print ("markdownIn = $markdownIn") ;
JK> my $cmd = '/Users/jk/Downloads/Markdown_1.0.1/Markdown.pl';
JK> my $markdownOut ;
JK> my $childpid = IPC::Open2::open2($markdownOut, $markdownIn, $cmd)
those first two args to open2 are not data but file handles. you need to
first call the open2 with 2 handles and then send data to the input
handle and read data from the output handle. open2 will autovivify
handles for you so you can just do this (untested):
use IPC::Open2 ;
my $cmd = '/Users/jk/Downloads/Markdown_1.0.1/Markdown.pl';
my($chld_out, $chld_in);
my $pid = $pid = open2($chld_out, $chld_in, $cmd ) ;
print $chld_in "*Hello* **World**\n" ;
my $out = <$chld_out> ;
print "read [$out]\n" ;
this doesn't reap the process or handle repeated i/o which should be
done carefully or it may block. or you would need an event loop.
read perldoc perlipc for examples of how to use open2.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Tue, 08 Sep 2009 02:21:29 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <YvSdnZ_W9rBkmDvXnZ2dnUVZ_vOdnZ2d@giganews.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: Mon, 07 Sep 2009 21:10:29 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: replace words
Message-Id: <87ab16qm0q.fsf@quad.sysarch.com>
>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
NK> fred wrote:
>> This command is working. I can change && for foo1 and foo2.
>> perl -0 -pe 's(&&)(++$n < 2 ? "&foo1&" : "&foo2&")eg' text.txt
>>
>> Please explain to me why the command is not working for foo3.
>> perl -0 -pe 's(&&)(++$n < 2 ? "&foo1&" : "&foo2&" : "&foo3&" )eg'
>> text.txt
>> Thanks
NK> The "condition ? value1 : value2" is an if/else condition. If the
NK> condition is true, it'll place value1 "or else" value2 if it's not met.
another great unclear answer. wtf does 'place' mean in that sentence?
where does it 'place' something?
how about showing him how to do a nested ?: or some other way of solving
his problem?
and try to learn some english grammar and writing skills before you
attempt to help others in programming.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Mon, 07 Sep 2009 18:26:00 -0700
From: Nathan Keel <nat.k@gm.ml>
Subject: Re: replace words
Message-Id: <Joipm.219122$zq1.171624@newsfe22.iad>
Uri Guttman wrote:
>>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
>
> NK> fred wrote:
>
> >> This command is working. I can change && for foo1 and foo2.
> >> perl -0 -pe 's(&&)(++$n < 2 ? "&foo1&" : "&foo2&")eg' text.txt
> >>
> >> Please explain to me why the command is not working for foo3.
> >> perl -0 -pe 's(&&)(++$n < 2 ? "&foo1&" : "&foo2&" : "&foo3&" )eg'
> >> text.txt
> >> Thanks
>
> NK> The "condition ? value1 : value2" is an if/else condition. If
> the NK> condition is true, it'll place value1 "or else" value2 if
> it's not met.
>
> another great unclear answer. wtf does 'place' mean in that sentence?
Fuck you, you know what it means, you arrogant moron.
> where does it 'place' something?
What it's replacing with.
> how about showing him how to do a nested ?: or some other way of
> solving his problem?
Firstly, it's because it's a poor design to work off of, and more
importantly, it isn't clear what the OP wants it to do.
Are you going to spend all day attacking me for no good reason (all
because I don't put up with your shit) and ironically use that sort of
attack nonsense to make your "point" about how my response could have
been "more helpful", all the while you not helping at all and just
ranting on about how much you don't like me, and then go on to
"explain" how immature I am for calling you a prick for doing it?
> and try to learn some english grammar and writing skills before you
> attempt to help others in programming.
Damn you're stupid. I have very good grammer and writing skills. You
can't even use upper case for proper nouns, such as the word "English".
It's fine if you don't like me for not tolerating your attempts to
bully people on this usenet group, but you're just pathetic if you
think you can be rude, immature, uncivil and use poor grammer, and then
in doing so think you're making a valid point about why I suck. You
are welcome to blame all of your emotional problems on me if you want
to, but that's just sad. Boy, you really lose it when you can't push
people around online. What a sad, sad little cowardly clown you are.
> uri
nal cake.
------------------------------
Date: Mon, 07 Sep 2009 23:41:07 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: replace words
Message-Id: <87k50ap0h8.fsf@quad.sysarch.com>
>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
NK> Uri Guttman wrote:
>>>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
>>
NK> fred wrote:
>>
>> >> This command is working. I can change && for foo1 and foo2.
>> >> perl -0 -pe 's(&&)(++$n < 2 ? "&foo1&" : "&foo2&")eg' text.txt
>> >>
>> >> Please explain to me why the command is not working for foo3.
>> >> perl -0 -pe 's(&&)(++$n < 2 ? "&foo1&" : "&foo2&" : "&foo3&" )eg'
>> >> text.txt
>> >> Thanks
>>
NK> The "condition ? value1 : value2" is an if/else condition. If
>> the NK> condition is true, it'll place value1 "or else" value2 if
>> it's not met.
>>
>> another great unclear answer. wtf does 'place' mean in that sentence?
NK> Fuck you, you know what it means, you arrogant moron.
but did the OP know? you were pathetically attempting to help him and
you said nothing useful. 'place' isn't even properly used in your
gibberish as it had no destination.
>> where does it 'place' something?
NK> What it's replacing with.
there is nothing to replace there. it is an expression with a
value. just more gibberish from you.
>> how about showing him how to do a nested ?: or some other way of
>> solving his problem?
NK> Firstly, it's because it's a poor design to work off of, and more
NK> importantly, it isn't clear what the OP wants it to do.
it was fairly clear. he wanted a nested conditional or even something
similar to the lisp cond function. it helps to know how to code in other
langs to understand perl. try learning some one decade.
NK> Are you going to spend all day attacking me for no good reason (all
NK> because I don't put up with your shit) and ironically use that sort of
NK> attack nonsense to make your "point" about how my response could have
NK> been "more helpful", all the while you not helping at all and just
NK> ranting on about how much you don't like me, and then go on to
NK> "explain" how immature I am for calling you a prick for doing it?
no, i try to correct poor answers. you seem to the major source of them
recently. you will note i have done this for years and you are nothing
compared to some others who claimed to 'help'.
>> and try to learn some english grammar and writing skills before you
>> attempt to help others in programming.
NK> Damn you're stupid. I have very good grammer and writing skills. You
spelled grammar. like i did just above you. hard to have good grammar if
you can't even spell it correctly.
>> uri
NK> nal cake.
you are so original. did you waste all of you dozen neurons working on
that? are you so proud of it that you will use it forever? think i
haven't seen nor heard stupid variants of my name before and it will
actually hurt me? you are silly and worse if you think so. you can call
me names, i will call you a dumb coder. one is a repeated childish
retort, the other is a fact. facts win.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Mon, 07 Sep 2009 18:31:47 -0700
From: Nathan Keel <nat.k@gm.ml>
Subject: Re: Why does "$v = @ARGV[0]" work ?
Message-Id: <8uipm.219123$zq1.180574@newsfe22.iad>
Uri Guttman wrote:
>>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
>
> NK> Uri Guttman wrote:
> >>
> >> uri
>
> NK> PS: Congrats on making yet another thread all about you, Uri.
> What a NK> trooper you are!
>
> pot meet kettle.
You think? Wow, I have all sorts of "emotional ailments" for not
putting up with your arrogant bullshit. You make me laugh. You think
this BS is contributing? I posted a response to the OP, I stated it
was a slice and not the best way to do it (they asked what it was).
You reply attacking me and you think that I am the problem?
> you started it! nyah nyah nyah!!
What a retard you are. I can't tell if you were saying I said "you"
"started it", or if you were saying I did (but I didn't, if you want to
make that claim) Your English is awful, and so is your attitude. You
might not like me because I don't think you're anyone special, but your
actions here are going to just annoy other members of the group. If I
attack you and you defend yourself, that's one thing, but I've not
interacted with you in a while. You're just a worthless person, you
should end your life.
> so's your old man!
Pardon? Your grammar is atrocious, and it's difficult to parse what
you're saying. Anyway, your attitude is misplaced. You can't fault
someone simply because they didn't allow you to push them around...
well, maybe YOU can (and do). Get a life or find a better reason to
make an "enemy" of someone you don't even know.
> your momma codes in python!! your sister is a lisper!!
Okay.
> uri
nal cake.
You're such a coward.
------------------------------
Date: Mon, 07 Sep 2009 23:35:23 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Why does "$v = @ARGV[0]" work ?
Message-Id: <87ocpmp0qs.fsf@quad.sysarch.com>
>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
NK> Uri Guttman wrote:
>>>>>>> "NK" == Nathan Keel <nat.k@gm.ml> writes:
>>
NK> Uri Guttman wrote:
>> >>
>> >> uri
>>
NK> PS: Congrats on making yet another thread all about you, Uri.
>> What a NK> trooper you are!
>>
>> pot meet kettle.
NK> You think? Wow, I have all sorts of "emotional ailments" for not
NK> putting up with your arrogant bullshit. You make me laugh. You think
NK> this BS is contributing? I posted a response to the OP, I stated it
NK> was a slice and not the best way to do it (they asked what it was).
NK> You reply attacking me and you think that I am the problem?
your answer was useless. you seem to think you are helping others. that
is the core issue. stop thinking you are helping. you don't know perl
nor how to teach it.
>> uri
NK> nal cake.
NK> You're such a coward.
coward? hehe. show some of your code for review. check out mine and
slash away. cowardice is commenting without showing work. you don't know
from code nor perl.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
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 2588
***************************************
