[28733] in Perl-Users-Digest
Perl-Users Digest, Issue: 10097 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 26 11:06:04 2006
Date: Tue, 26 Dec 2006 08:05:05 -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 Tue, 26 Dec 2006 Volume: 10 Number: 10097
Today's topics:
Blather-Adjusting Programs vjp2.at@at.BioStrategist.dot.dot.com
Re: Blather-Adjusting Programs vjp2.at@at.BioStrategist.dot.dot.com
Re: Blather-Adjusting Programs <hmessinger.removethis@comcast.net>
Re: Negative Regular Expression <uri@stemsystems.com>
new CPAN modules on Tue Dec 26 2006 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Using clearcase command in perl script mnt006@gmail.com
Re: Using clearcase command in perl script <mritty@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 26 Dec 2006 14:44:46 +0000 (UTC)
From: vjp2.at@at.BioStrategist.dot.dot.com
Subject: Blather-Adjusting Programs
Message-Id: <emrcgu$aia$1@reader2.panix.com>
You folks mean to tell me there's no program out there that would take a
file of simple text and blatherise it to the level of another "reference"
file? Or Adjust the "Fog Index" of a text file up or down from its input
level. I'm totally serious. I'm tired of fighting. I just want to "get
along".
I have one idea: you score each verb and noun on, say, five, different
scales, then you pile on similarly ranked adverbs and adjectives until you
meet the volume requirement. Or you remove accordingly. In MS-Word type
environments, you score less necessary modifiers, say , with orange-colored
undersquiggles, the less necessary, the more undersquiggles.
Message-ID: <dn55rq$mov$1@reader2.panix.com>
I'm sure I've seen programs that generate blather but now I can't find
one. I'm stuck in a wierd situation that comes up often enough: Some
third-worlders insist you write pretentious casuistry when a few simple words
are enough. It is sad in these day of "Fog Index" that we have people who are
commitedly ideological and even theologically dogmatic about making prose
incomprehensibly obfuscated and complicated. I want it in perl so it can be
extremely portable.
However, I want something I can control. For example, when it sees the
word "customer" or "strategy" it should randomly chose one of three flowing
phrases. I can write a simple one-to-one in sed, but I really hope some
ingenious soul has already compiled a blatherisation table that I only need
to tweak. The issue is the text should require no more than, say, ten
percent editing to make it seem like it came from a genuinely glib
casuistrous bullshit artist.
I wouldn't mind if the program is ingenious enough to go both ways, or
even to be adjustable (ie, "please set the fog index"). I am confronted with
enough blathermaniacs and antiblathermaniacs to make my life way too
complicated. By the time I get used to one lunatic, I have to instead conform
to the other.
Message-ID: <do5j5i$2da$3@reader1.panix.com>
I think you could broadly generalise the most common writing styles are:
1. Cryptic misappropriated connotation (demanded by "scholars")
2. Telegraphic commercial (Taught by "Communications" programs)
3. Latinate bureaucratic (demanded by 3rd world bureaucrats)
4. Literary Synonymania (demanded by "English" professors/teachers)
And these variances seem to be used to discriminate and segregate
dogmatically and unfairly. "Can't we just all get along?"
Message-ID: <dnvsup$p3u$1@reader1.panix.com>
I went hunting on google for "chatterbot perl knowledge base". I "knew"
Hugh Kenner back on BiX ca 1988. Foggy is a riot, but not what I needed,
though I think sometime it may prove valuable when frustration with fools
triggers my evil streak. I need foggy with a twist - a knowledge base I can
tweak like foggy, but it should take a simple paragraph and turn it into a
long blatherous paper that I can then spend a few minutes editing and it will
say pretty much the same thing as my simple paragraph. For example I write
"The customer is a petunia" and it writes "Our customers are very important
to us. One of our multifarous customers has proven to be a
petunia. Wheretofore and heretofore, this important, vaulable and significant
datum will be assessed strategically and applied to our models wherefrom we
shall therefore optimise our tactics, strategy and operations so that we
fully capture the economic benefits derivable from this customer." One form
would work with a knowledge base where it is triggered by words like customer
and petunia into random but reasonably meaningful ramblings. The other would
be even better if it took a file with writing similar to the target and
transformed the source using the target as a model (for style and size). I
would really wish this was in perl so I could use it on the fly anywhere!
nyc.transit Tue, 20 Dec 2005 23:19:28 +0000 (UTC)
You remind me of how my folks got mistreated. They spoke with a heavy
accent but at the university level. A lot of academics would love to
converse endlessly with their precise and inquiring minds. Some "customer
service" types would just hang up the phone when they heard the accent. One
of my English teachers couldn't get over it how my folks had the nerve to
correct her spelling.
I was born here and once I had a boss say that the reason I disgreed on
policy issues was I needed to improve my writing since I was Greek and sent
me to a writing class (she was Cuban and spoke with an accent, but I don't
have an accent). Once someone asked me "You speak English so well, when did
you come here" I looked at my watch and said "Oh, about 120 yrs ago."
(Technically true, though my stowaway ancestors got sent back a month later)
I once went to speak to a dean about something and he mentioned the essence
of the conversation to a reporter and I saw in print that he described me as
a foreign student (he, too, had an accent and was foreign born). When a
previous president of my alma mater was introduced to alums, he saw my name
badge and said "Ohhhh, Greek" shaking his head knowingly as I was seriously
thinking of swatting him on the head like a fly.
- = -
Vasos Panagiotopoulos, Columbia'81+, Reagan, Mozart, Pindus, BioStrategist
http://ourworld.compuserve.com/homepages/vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---
[Homeland Security means private firearms not lazy obstructive guards]
[Urb sprawl confounds terror] [Remorse begets zeal] [Windows is for Bimbos]
------------------------------
Date: Tue, 26 Dec 2006 14:50:46 +0000 (UTC)
From: vjp2.at@at.BioStrategist.dot.dot.com
Subject: Re: Blather-Adjusting Programs
Message-Id: <emrcs5$r1$1@reader2.panix.com>
BTW, the beginning of third book of Aristotle's Rhetoric explains
quite well why one should NOT use blather. It says exactly what my
"corporate writing" instructor said while trying to disabuse me of bad
habits had forced on my at the University.
- = -
Vasos Panagiotopoulos, Columbia'81+, Reagan, Mozart, Pindus, BioStrategist
http://ourworld.compuserve.com/homepages/vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---
[Homeland Security means private firearms not lazy obstructive guards]
[Urb sprawl confounds terror] [Remorse begets zeal] [Windows is for Bimbos]
------------------------------
Date: Tue, 26 Dec 2006 10:50:38 -0500
From: Harlan Messinger <hmessinger.removethis@comcast.net>
Subject: Re: Blather-Adjusting Programs
Message-Id: <4vcun0F1bkca7U1@mid.individual.net>
vjp2.at@at.BioStrategist.dot.dot.com wrote:
> You folks mean to tell me there's no program out there that would take a
> file of simple text and blatherise it to the level of another "reference"
> file?
"You folks mean?" Did someone here (sci.lang) say that?
> Or Adjust the "Fog Index" of a text file up or down from its input
> level. I'm totally serious. I'm tired of fighting. I just want to "get
> along".
Fighting what?
> I have one idea: you score each verb and noun on, say, five, different
> scales, then you pile on similarly ranked adverbs and adjectives until you
> meet the volume requirement. Or you remove accordingly. In MS-Word type
> environments, you score less necessary modifiers, say , with orange-colored
> undersquiggles, the less necessary, the more undersquiggles.
If it's so simple, go ahead and make it happen.
(Are you under the impression that software exists that has that degree
of facility with human language?)
------------------------------
Date: Mon, 25 Dec 2006 23:29:37 -0500
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Negative Regular Expression
Message-Id: <x71wmnuvny.fsf@mail.sysarch.com>
>>>>> "r" == rand007 <rand007@gmail.com> writes:
first off don't top post. read the group guidelines which are posted
regularly.
r> I found the magic look ahead expression that achieves my whish!!!
r> it goes like this: /^(?!.*strsuffix$)/
r> This expression matches any string that does not end with "srtsuffix".
that is a negative lookahead and it may work here but it not the same as
a negative match which is probably what you want and which others have
shown you.
also that regex is anchored at both ends which is not needed. it uses a
fixed 'strsuffix' which is not a variable. if the suffix has a . in it
and that is not escaped than it will fail with bar.xstrsuffix. my point
is that you seemed to have lucked into this solution without
understanding it nor getting the responses. read perlre more and learn
about how to properly match a suffix or a set of them.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
------------------------------
Date: Tue, 26 Dec 2006 05:42:11 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Dec 26 2006
Message-Id: <JAv96B.H5I@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.
Catalyst-Plugin-FormValidator-Simple-Auto-0.10
http://search.cpan.org/~typester/Catalyst-Plugin-FormValidator-Simple-Auto-0.10/
Smart validation with FormValidator::Simple
----
Catalyst-Plugin-Upload-Image-Magick-0.03
http://search.cpan.org/~zigorou/Catalyst-Plugin-Upload-Image-Magick-0.03/
Image information plugin for Catalyst::Request::Upload
----
Devel-SawAmpersand-0.31
http://search.cpan.org/~andk/Devel-SawAmpersand-0.31/
Perl extension querying PL_sawampersand variable
----
HTTP-SimpleLinkChecker-1.11
http://search.cpan.org/~bdfoy/HTTP-SimpleLinkChecker-1.11/
Check the HTTP response code for a link
----
LaTeX-Pod-0.01
http://search.cpan.org/~schubiger/LaTeX-Pod-0.01/
Transform LaTeX source files to POD (Plain old documentation)
----
LaTeX-Pod-0.02
http://search.cpan.org/~schubiger/LaTeX-Pod-0.02/
Transform LaTeX source files to POD (Plain old documentation)
----
LaTeX-Pod-0.03
http://search.cpan.org/~schubiger/LaTeX-Pod-0.03/
Transform LaTeX source files to POD (Plain old documentation)
----
LaTeX-TOM-0.4
http://search.cpan.org/~schubiger/LaTeX-TOM-0.4/
A module for parsing, analyzing, and manipulating LaTeX documents.
----
Language-Indonesia-0.02
http://search.cpan.org/~dns/Language-Indonesia-0.02/
Write Perl program in Bahasa Indonesia.
----
Metai-Kalendorius-0.02
http://search.cpan.org/~kyoshu/Metai-Kalendorius-0.02/
Lithuanian calendar.
----
Statistics-Smoothing-SGT-2.0.1
http://search.cpan.org/~bjoernw/Statistics-Smoothing-SGT-2.0.1/
A Simple Good-Turing (SGT) smoothing implementation
----
Text-Hatena-0.16
http://search.cpan.org/~jkondo/Text-Hatena-0.16/
Perl extension for formatting text with Hatena Style.
----
Text-vFile-toXML-0.01
http://search.cpan.org/~kulp/Text-vFile-toXML-0.01/
Convert vFiles into equivalent XML
----
WWW-20Q-0.02
http://search.cpan.org/~kirsle/WWW-20Q-0.02/
Perl interface to the classic 20 Questions game as provided by 20Q.net
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/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: 26 Dec 2006 08:10:07 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.7 $)
Message-Id: <4590d8de$0$81351$ae4e5890@news.nationwide.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.7 $)
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.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 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_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: 26 Dec 2006 07:28:20 -0800
From: mnt006@gmail.com
Subject: Using clearcase command in perl script
Message-Id: <1167146900.465495.80350@73g2000cwn.googlegroups.com>
Hi,
I am having list of files in an array. Example.
array[0]=/vobs/abc
array[1]=/vobs/abc/foo1.c
array[2]=/vobs/abc/foo2.c
.......
I want to perform clearcase check out command on this list of files.
Can anyone suggest how to do this using perl?
Thanks.
------------------------------
Date: 26 Dec 2006 07:36:48 -0800
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: Using clearcase command in perl script
Message-Id: <1167147408.182972.201600@79g2000cws.googlegroups.com>
mnt...@gmail.com wrote:
> I am having list of files in an array. Example.
> array[0]=/vobs/abc
> array[1]=/vobs/abc/foo1.c
> array[2]=/vobs/abc/foo2.c
Please type real code, even in examples.
my @array = qw(/vobs/abc /vobs/abc/foo1.c /vobs/abc/foo2.c);
> I want to perform clearcase check out command on this list of files.
> Can anyone suggest how to do this using perl?
Perhaps you could describe how a "clearcase check out command" works or
at least looks? Is it something that can only accept one filename as
the argument? In that case, do something like:
foreach my $file (@array) {
system("clearcase_checkout_command", $file);
}
Is it something that accepts multiple file names, all specified on the
command line? Then do something like:
system("clearcase_checkout_command", @array);
Until you tell us how to do the basic task, it's rather difficult to
help you modify it for the real pursuit...
Paul Lalli
------------------------------
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 10097
****************************************
