[18518] in Perl-Users-Digest
Perl-Users Digest, Issue: 686 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 13 00:06:07 2001
Date: Thu, 12 Apr 2001 21:05:23 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <987134722-v10-i686@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Thu, 12 Apr 2001 Volume: 10 Number: 686
Today's topics:
.htaccess (Stuart Wildish)
Re: .htaccess <keesh@users.pleaseremovethisbit.sourceforge.net>
Re: A CGI question (Randal L. Schwartz)
Re: A CGI question <comdog@panix.com>
Re: A CGI question <flavell@mail.cern.ch>
Re: A CGI question <camerond@mail.uca.edu>
Re: A CGI question (Tad McClellan)
Re: A CGI question (Randal L. Schwartz)
Re: A CGI question <flavell@mail.cern.ch>
Re: A CGI question (Randal L. Schwartz)
Re: A CGI question (Logan Shaw)
Re: A fork() problem under W98 <Jonathan.L.Ericson@jpl.nasa.gov>
ANNOUNCE: cpancd 1.00 -- CPAN on CD (Johan Vromans)
ANNOUNCE: Spreadsheet::WriteExcel 0.31 (John McNamara)
Announcing: TESTING COMPUTER SOFTWARE (TCS2001) Confere (Peter Zuckerman)
Can File::Find selectively search subdirs? <Robert.H.Lowe@X-no.spam-X.lawrence.edu>
Re: Can File::Find selectively search subdirs? (Randal L. Schwartz)
Re: Can File::Find selectively search subdirs? (Randal L. Schwartz)
Re: Can File::Find selectively search subdirs? (Mark Jason Dominus)
Re: Can File::Find selectively search subdirs? <Robert.H.Lowe@X-no.spam-X.lawrence.edu>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 12 Apr 2001 19:11:21 GMT
From: mr_cereyDOESNOTWANTSPAM@yahoo.co.uk (Stuart Wildish)
Subject: .htaccess
Message-Id: <3ad5fcae.8104067@news.demon.co.uk>
hallo folks.
Sorry if this is the wrong group to be posting in, but it looked like
the best option to me.
Anyway, i've got a clan website with BarrysWorld who give cgi and
htaccess with their web sites.
I want my clan members to be able to log into the .htaccess area (a
folder called private) and then be able to update news and their
profiles without having to pass the information as to who they are to
my perl script with the form.
Therefore is there a way to take who the person logged into the
/private/ folder is from the HTTP header or something?
does that make sense?
TIA
stu
------------------------------
Date: Thu, 12 Apr 2001 20:29:24 +0100
From: "Ciaran McCreesh" <keesh@users.pleaseremovethisbit.sourceforge.net>
Subject: Re: .htaccess
Message-Id: <9b4rc6$nr4$1@news7.svr.pol.co.uk>
In article <3ad5fcae.8104067@news.demon.co.uk>,
mr_cereyDOESNOTWANTSPAM@yahoo.co.uk wrote:
> Sorry if this is the wrong group to be posting in
It is. You probably want the cgi newsgroup.
> Anyway, i've got a clan website with BarrysWorld who give cgi and
> htaccess with their web sites. I want my clan members to be able to log
> into the .htaccess area (a folder called private) and then be able to
> update news and their profiles without having to pass the information as
> to who they are to my perl script with the form. Therefore is there a
> way to take who the person logged into the
> /private/ folder is from the HTTP header or something?
There is.
What, you want to know what it is? Go read rfc2616 and rfc2617.
Especially the bit on headers.
And rtfd before asking next time... Thanks.
--
Ciaran McCreesh
mail: keesh@users.sourceforge.net
web: http://www.opensourcepan.com/
------------------------------
Date: 12 Apr 2001 08:13:42 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: A CGI question
Message-Id: <m166garw0p.fsf@halfdome.holdit.com>
>>>>> "Si" == Si Ballenger <shb@vnet.net> writes:
Si> As an alternative, the really upset readers can save on their
Si> Prozac bills by *just not reading* an article titled "A CGI
Si> question", or if they they have absolutely no control over
Si> themselves, they can put "CGI" in their kill file. I know it is a
Si> struggle for some, but it can be done. ;-)
<sarcasm>
Yes, why not just eliminate groups altogether, and have ONE BIG GROUP
for ALL OF USENET, and we can select things based on their SUBJECT LINE!
Yes, what a novel idea. Fantastic! We'll implement it at once!
</sarcasm>
The reason we *have* groups is to allow reasonably accomodating mature
people to segregate the flow of Usenet conversation into topic areas,
so that people who are, for example, interested in Perl topics *other*
than CGI (which has its own group) can subscribe to CLPM and not
CIWAC.
If you aren't willing to play by the rules, you apparently aren't
mature enough for Usenet. You'll be quickly targeted, and "plonked":
the public declaration to other Usenet users that you are not playing
by the rules, and should be ignored *as an author*.
So the continued effort here to promote *on topic* conversation is for
the rest of us to be able to sort the mature people from the immature
people. Be careful how you describe yourself, lest you get killfiled.
Just another guy trying to make Usenet work since 1980 (yes, 1980!)),
--
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: Thu, 12 Apr 2001 11:29:44 -0400
From: brian d foy <comdog@panix.com>
Subject: Re: A CGI question
Message-Id: <comdog-38AC95.11294412042001@news.panix.com>
In article <3ad5c20e.504241799@166.82.1.9>, shb@vnet.net wrote:
> As an alternative, the really upset readers can save on their
> Prozac bills by *just not reading* an article titled "A CGI
> question", or if they they have absolutely no control over
> themselves, they can put "CGI" in their kill file. I know it is a
> struggle for some, but it can be done. ;-)
that's not really an option. it might have been before every
usenet post was archived and searchable, but not any more.
bad information lives forever.
--
brian d foy <comdog@panix.com>
------------------------------
Date: Thu, 12 Apr 2001 18:23:29 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: A CGI question
Message-Id: <Pine.LNX.4.30.0104121817520.408-100000@lxplus003.cern.ch>
On Thu, 12 Apr 2001, Si Ballenger wrote:
[pointlessly quotes my entire posting in order to say:]
> As an alternative, the really upset readers can save on their
> Prozac bills by *just not reading* an article titled "A CGI
> question",
I'm happy to respond to CGI questions in their right place.
Sometimes, I even feel competent to do so. ;-)
When I come here, I want to talk about Perl, just like the regulars
want. About Perl language programming. Not about netiquette (there's
been far too much of that recently, but sadly I concede that some of
it has been necessary), not about CGI, not about configuring web
servers, not about writing HTML just because the HTML happens to be
written by a Perl script...
> I know it is a
> struggle for some, but it can be done. ;-)
Application approved.
bye
------------------------------
Date: Thu, 12 Apr 2001 17:01:48 -0500
From: Cameron Dorey <camerond@mail.uca.edu>
Subject: Re: A CGI question
Message-Id: <3AD625CC.6A73A638@mail.uca.edu>
"Randal L. Schwartz" wrote:
>
> >>>>> "Logan" == Logan Shaw <logan@cs.utexas.edu> writes:
>
> Logan> Just a random comment, but maybe one way of addressing the
> Logan> problem is to create something like comp.lang.perl.www, a
> Logan> group for discussing web development using Perl.
>
> This has been proposed numerous times. People that propose it nearly
> always forget the next point...
>
> Logan> Yes, it would overlap c.i.w.a.c some, but I don't think that,
> Logan> by itself, that is enough to conclude it shouldn't exist.
>
> ... that in fact, nearly all of the issues related to programming CGI
> with Perl are about CGI, not about Perl. So if anything, the group
> name should be c.i.w.a.c.PERL, not c.l.p.CGI. The small Perl-specific
> issues around CGI are in fact welcome in CLPM, and are not enough to
> justify a separate group for it. I've never seen anyone shooed away
> for asking a legitimate *Perl* question about CGI in CLPM.
You know, this thing comes up so darn often, it makes me wonder just how
so many with CGI questions come directly to clpm. Since they
(supposedly) are writing in Perl, do they do a newsgroup search for
something with Perl in the name? If so, maybe ciwac.perl wouldn't be
that bad an idea as it might send some/nearly all/all of them there
first (but I'm not going to do the legwork for it).
Cameron
--
Cameron Dorey
Associate Professor of Chemistry
University of Central Arkansas
Phone: 501-450-5938
camerond@mail.uca.edu
------------------------------
Date: Thu, 12 Apr 2001 15:29:31 -0400
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: A CGI question
Message-Id: <slrn9dc0gr.ema.tadmc@tadmc26.august.net>
Si Ballenger <shb@vnet.net> wrote:
>they can put "CGI" in their kill file.
I don't do that because that does not prove that it is off-topic,
and I don't want to miss a Perl question only because Perl happens
to be applied to CGI programming.
>I know it is a
>struggle for some, but it can be done. ;-)
The smiley didn't work.
I have put "shb@vnet.net" in my killfile instead. So long.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 12 Apr 2001 15:21:52 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: A CGI question
Message-Id: <m1bsq1pxmn.fsf@halfdome.holdit.com>
>>>>> "Cameron" == Cameron Dorey <camerond@mail.uca.edu> writes:
Cameron> You know, this thing comes up so darn often, it makes me wonder just how
Cameron> so many with CGI questions come directly to clpm. Since they
Cameron> (supposedly) are writing in Perl, do they do a newsgroup search for
Cameron> something with Perl in the name? If so, maybe ciwac.perl wouldn't be
Cameron> that bad an idea as it might send some/nearly all/all of them there
Cameron> first (but I'm not going to do the legwork for it).
Well, you're supposed to read a group for three weeks before posting
to it for the first time. In that time, you'd see what the culture is
like, what questions generally get asked and answered, and what FAQs
are verboten as offtopic. I know that at least once a week or so, we
send a CGI question to CIWAC. So if someone's playing at the adult
level, we got nothing to worry about for the 17 others who have seen
that and now know better.
The problem is "those meddling kids"[1] who don't play by the very
reasonable rules.
CIWAC is completely accepting of Perl questions. I've never seen
anyone shooed away from there for asking a Perl related CGI question,
except when they ask a "pure perl" question. And again, there's not
enough Perl-specific CGI questions asked there to warrant a
CIWAC.perl.
The problem we have is that most people really can't tell whether it's
a Perl question, or a CGI question. And CIWAC is slightly harder to
find than CLPM (apparently), so CLPM seems to take the brunt of the
mistakes.
[1] Scooby Doo reference intended.
--
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: Fri, 13 Apr 2001 00:23:30 +0200
From: "Alan J. Flavell" <flavell@mail.cern.ch>
Subject: Re: A CGI question
Message-Id: <Pine.LNX.4.30.0104122352210.3071-100000@lxplus003.cern.ch>
On 12 Apr 2001, Logan Shaw wrote:
> Just a random comment, but maybe one way of addressing the
> problem is to create something like comp.lang.perl.www, a
> group for discussing web development using Perl.
I shall express myself frankly. If this disturbs you, feel free to
leave now.
Over a number of years I've had productive contacts with quite a
number of people over CGI issues. Almost all of them have been on
c.i.www.*** groups. Occasionally I've also had useful contacts on CGI
issues on c.l.perl.*, but for the most part I have found those
contacts unsatisfactory (and I still have several open issues on Perl
CGI FAQs, and am slowly coming to the conclusion that I think perlfaq9
in its present form should be abolished...)
I come here to learn about Perl, and for the most part I have not been
disappointed (albeit most of what I have learned has been as a lurker,
on threads in which I have not needed to say anything).
In quite a number of cases (they know who they are ;-) I'm dealing
with the same people on both groups, but the context is so
different...
If you want to create your new group as a trashcan to which you hope
to attract newbies so that they don't upset the local denizens, then I
suppose reluctantly that you might have a point. But if you hope to
educate newbies to become productive participants in the usenet
experience - and as an irredeemable idealist I'm still hoping for that
- then I'm afraid I have to say I think you're misguided, and the
balance would be negative for all concerned.
> Yes, it would overlap c.i.w.a.c some, but I don't think that,
> by itself, that is enough to conclude it shouldn't exist.
I'm sorry, but I disagree. It would divide the effort, not so very
much different than the c.l.p.misc versus alt.perl dichotomy, and
benefit only those who have no interest in making progress in the
great "usenet concordat" - but rather believe they can change anything
that doesn't suit their own uninformed prejudices, irrespective of the
big picture, and "hold court" on their pet group exchanging cargo cult
recipes - undisturbed by those who understand the fundamentals.
I'm not trying to say that the usenet structure is ideal - far from
it. What I _am_ trying to say is that we do better to work _with_ the
structure as far as possible, and only re-organise it when all else
fails. I've experienced many re-organisations during the decade or so
that I've been participating. NONE of them (I can confidently say)
have helped those who refuse to read the groups and their FAQs to find
the appropriate group to post. SOME of them have been successful and
appropriate in helping experienced users to structure their discussion
- others have, with hindsight, been pointless, and have merely
fragmented the discussion.
Being a long-term denizen of c.i.w.authoring.html, I am only too
keenly aware that the magic term "html" attracts absolutely everything
that has the remotest relevance to the WWW, and hardly ever gets to
discuss HTML as such. c.l.perl.misc is at least spared that
indignity. Long may it discuss the Perl language, and (when
necessary) help CGI users to find the right group to post.
all the best
------------------------------
Date: 12 Apr 2001 14:22:24 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: A CGI question
Message-Id: <m1n19lq0dr.fsf@halfdome.holdit.com>
>>>>> "Logan" == Logan Shaw <logan@cs.utexas.edu> writes:
Logan> In article <m166garw0p.fsf@halfdome.holdit.com>,
Logan> Randal L. Schwartz <merlyn@stonehenge.com> wrote:
>> The reason we *have* groups is to allow reasonably accomodating mature
>> people to segregate the flow of Usenet conversation into topic areas,
>> so that people who are, for example, interested in Perl topics *other*
>> than CGI (which has its own group) can subscribe to CLPM and not
>> CIWAC.
Logan> Just a random comment, but maybe one way of addressing the
Logan> problem is to create something like comp.lang.perl.www, a
Logan> group for discussing web development using Perl.
This has been proposed numerous times. People that propose it nearly
always forget the next point...
Logan> Yes, it would overlap c.i.w.a.c some, but I don't think that,
Logan> by itself, that is enough to conclude it shouldn't exist.
... that in fact, nearly all of the issues related to programming CGI
with Perl are about CGI, not about Perl. So if anything, the group
name should be c.i.w.a.c.PERL, not c.l.p.CGI. The small Perl-specific
issues around CGI are in fact welcome in CLPM, and are not enough to
justify a separate group for it. I've never seen anyone shooed away
for asking a legitimate *Perl* question about CGI in CLPM.
Logan> Of course, it's just a thought. It might not even be an
Logan> original one.
You got that one, buddy.
--
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: 12 Apr 2001 15:51:17 -0500
From: logan@cs.utexas.edu (Logan Shaw)
Subject: Re: A CGI question
Message-Id: <9b54g5$427$1@charity.cs.utexas.edu>
In article <m166garw0p.fsf@halfdome.holdit.com>,
Randal L. Schwartz <merlyn@stonehenge.com> wrote:
>The reason we *have* groups is to allow reasonably accomodating mature
>people to segregate the flow of Usenet conversation into topic areas,
>so that people who are, for example, interested in Perl topics *other*
>than CGI (which has its own group) can subscribe to CLPM and not
>CIWAC.
Just a random comment, but maybe one way of addressing the
problem is to create something like comp.lang.perl.www, a
group for discussing web development using Perl.
Yes, it would overlap c.i.w.a.c some, but I don't think that,
by itself, that is enough to conclude it shouldn't exist.
Newsgroups are supposed to divide people up so that people
who are talking about unrelated things don't have to see
each others' traffic, and also so that people who want to
talk about related things can. Having two groups that
overlap a little can be detrimental to the latter, but in
this case I think the former benefit might outweigh that.
Of course, it's just a thought. It might not even be an
original one.
- Logan
--
my your his her our their _its_
I'm you're he's she's we're they're _it's_
------------------------------
Date: 13 Apr 2001 00:47:08 +0000
From: Jon Ericson <Jonathan.L.Ericson@jpl.nasa.gov>
Subject: Re: A fork() problem under W98
Message-Id: <86y9t54odv.fsf@jon_ericson.jpl.nasa.gov>
nimchu@yahoo.com (Nim Chu) writes:
> I use ActiveState perl 5.6 build 623. My code looks like this:
> Uset Tk;
^ ^
You should copy and paste from working code -- who knows what other
typos you made?
If the problem is really just with fork, you should be able to write a
small test script that doesn't use Tk, yet fails. If it is a Tk+fork
problem, you might post a minimal, self-contained script to
comp.lang.perl.tk. If it is a Windows problem, you might contact
ActiveState.
Jon
------------------------------
Date: 12 Apr 2001 21:19:25 +0200
From: JVromans@Squirrel.nl (Johan Vromans)
Subject: ANNOUNCE: cpancd 1.00 -- CPAN on CD
Message-Id: <tdc41f8jahmf33@corp.supernews.com>
CPAN on a CD? But CPAN is almost 900Mb!
cpancd is a Perl program that creates an ISO image to burn on a CD. It
is intended to be used to create CD-rommable snapshots of CPAN.
It generates a subset of all CPAN files, by omitting older versions of
packages.
Currently (April 2001) the size of CPAN is about 880Mb, the generated
subset just over 630Mb.
URL: http://search.cpan.org/search?mode=dist&query=cpancd
This program requires the mkisofs program. This is part of the
cdrtools package widely available. See, for example,
ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/
----------------------------------------------------------------------------
Johan Vromans jvromans@squirrel.nl
Squirrel Consultancy Haarlem, the Netherlands
http://www.squirrel.nl http://www.squirrel.nl/people/jvromans
PGP Key 2048/4783B14D http://www.squirrel.nl/people/jvromans/pgpkey.html
----------------------- "Arms are made for hugging" ------------------------
------------------------------
Date: Thu, 12 Apr 2001 17:57:09 GMT
From: jmcnamara@cpan.org (John McNamara)
Subject: ANNOUNCE: Spreadsheet::WriteExcel 0.31
Message-Id: <tdc42tun36453@corp.supernews.com>
======================================================================
ANNOUNCE
Spreadsheet::WriteExcel version 0.31 has been uploaded to CPAN.
======================================================================
NAME
Spreadsheet::WriteExcel - Write formatted text and numbers to a
cross-platform Excel binary file.
======================================================================
CHANGES
Important bug fixes in the implementation of formulas. If you are
using formulas with Spreadsheet::WriteExcel you *should* upgrade
to this version.
You can now pass a filehandle to the new() constructor. Amongst
other things this will allow you to use the module with mod_perl.
tie *XLS, 'Apache';
my $workbook = Spreadsheet::WriteExcel->new(\*XLS);
Formulas and functions can now reference other worksheets in the
same workbook:
$worksheet->write(0, 0, '=MAX(Sheet2:Sheet3!B1:B9)');
Worksheet methods can now use Excel A1 notation:
$worksheet->write('H1', 200);
$worksheet->write('H2', '=H7+1');
======================================================================
DESCRIPTION
The Spreadsheet::WriteExcel module can be used create a cross-
platform Excel binary file. Multiple worksheets can be added to a
workbook and formatting can be applied to cells. Text, numbers,
formulas and hyperlinks can be written to the cells.
The Excel file produced by this module is compatible with Excel 5,
95, 97 and 2000.
The module will work on the majority of Windows, UNIX and
Macintosh platforms. Generated files are also compatible with the
Linux/UNIX spreadsheet applications OpenOffice, Gnumeric and XESS.
The generated files are not compatible with MS Access.
This module cannot be used to read an Excel file. See
Spreadsheet::ParseExcel or look at the main documentation for some
suggestions. This module cannot be uses to write to an existing
Excel file.
======================================================================
SYNOPSIS
To write a string, a formatted string, a number and a formula to
the first worksheet in an Excel workbook called perl.xls:
use Spreadsheet::WriteExcel;
# Create a new Excel workbook
my $workbook = Spreadsheet::WriteExcel->new("perl.xls");
# Add a worksheet
$worksheet = $workbook->addworksheet();
# Add and define a format
$format = $workbook->addformat(); # Add a format
$format->set_bold();
$format->set_color('red');
$format->set_align('center');
# Write a formatted and unformatted string
$col = $row = 0;
$worksheet->write($row, $col, "Hi Excel!", $format);
$worksheet->write(1, $col, "Hi Excel!");
# Write a number and a formula using A1 notation
$worksheet->write('A3', 1.2345);
$worksheet->write('A4', '=SIN(PI()/4)');
======================================================================
INSTALLATION
Method 1
Download the zipped tar file from one of the following:
http://search.cpan.org/search?dist=Spreadsheet-WriteExcel
http://theoryx5.uwinnipeg.ca/mod_perl/cpan-search?idinfo=154
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/J/JM/JMCNAMARA/
Unzip the module as follows or use winzip:
tar -zxvf Spreadsheet-WriteExcel-0.xx.tar.gz
The module can be installed using the standard Perl procedure:
perl Makefile.PL
make
make test
make install # You may need to be root
make clean # or make realclean
Windows users without a working "make" can get nmake from:
ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe
Method 2
If you have CPAN.pm configured you can install the module as
follows:
perl -MCPAN -e "install 'Spreadsheet::WriteExcel'"
Method 3
ActivePerl users can use PPM as follows:
C:\> ppm
PPM> set repository tmp
http://homepage.eircom.net/~jmcnamara/perl
PPM> install Spreadsheet-WriteExcel
PPM> quit
C:\>
If this fails try the following:
PPM>install
http://homepage.eircom.net/~jmcnamara/perl/Spreadsheet-WriteExcel.ppd
If you wish to perform a local PPM install you can get the files
from:
http://homepage.eircom.net/~jmcnamara/perl/Spreadsheet-WriteExcel.ppd
http://homepage.eircom.net/~jmcnamara/perl/Spreadsheet-WriteExcel-0.xx-PPM.tar.gz
======================================================================
REQUIREMENTS
This module requires Perl 5.005 (or later) and Parse::RecDescent:
http://search.cpan.org/search?dist=Parse-RecDescent
======================================================================
AUTHOR
John McNamara (jmcnamara@cpan.org)
--
------------------------------
Date: Thu, 12 Apr 2001 09:19:34 -0500
From: pazpax@clark.net (Peter Zuckerman)
Subject: Announcing: TESTING COMPUTER SOFTWARE (TCS2001) Conference -- Keynote Speakers and Workshops
Message-Id: <pazpax-1204010919340001@sdn-ar-005dcwashp250.dialsprint.net>
The keynote speakers and workshops/tutorials of the "18th International
Conference on TESTING COMPUTER SOFTWARE" (June 18-22, 2001; Washington,
DC, USA) will address major issues of concern to the developers and users
of software. The theme of the Conference "Meeting the New Challenges of
Testing" is highly relevant to the emerging and continuing needs of the
software development profession, and the users of computer software at all
levels.
The Conference is organized in cooperation with:
Association for Computing Machinery (ACM) SIGSoft
American Society for Quality (ASQ) Software Division
IEEE Reliability Society
Software Technology Support Center (STSC)
Conference Program is by Meredith Consultants
Conference Management by U.S. Professional Development Institute
GENERAL SESSIONS and KEYNOTE SPEAKERS:
"Real Time Priority and Risk Management for World Class Software Quality"
by Tom Gilb
"Is That Your Final Answer? Surviving Cross Examination in the Courtroom"
by Warren S. Reid
"Efficient Testing with a Measure to Select Testing Strategies"
by John Musa
"Educators Join the Fray -- Tester Training for Undergraduates"
by Edward L. Jones
"A World-Wide Web of Intrigue -- Deceptive Testing"
by Simon Mills
"Wrap-up Session: Conference Reflections" by Marnie Hutcheson
PRE-CONFERENCE WORKSHOPS and TUTORIALS (June 18-19) will present
comprehensive technical sessions for software testing practitioners:
WORKSHOPS (2 days)
1. "MITs Test Management Method" by Marnie Hutcheson
2. "Fundamentals of Testing Software-Intensive Systems" by Selim Aissi
TUTORIALS (1 day)
3. "Overview of Testing" by Simon Mills
4. "Test Planning Workshop" by Ross Collard
5. "The Automated Testing Lifecycle Methodology" by Elfriede Dustin
6. "Test Case Administration: Using XML to Exchange Test Case
Information Between the Business and Test Domains" by Hans Hartmann
7. "Evolutionary Project Management: How to Get Early Delivery and
Project" by Tom Gilb
8. "More Reliable Software Faster and Cheaper" by John Musa
9. "Software Verification and Validation: An Overview for Practitioners"
by Steven R. Rakitin
10. "Guided Inspections" by Melissa L. Russ
In addition, thirty-two CONCURRENT SESSIONS will be divided into four
parallel track sessions, presenting an extensive variety of management,
technical and research topics and issues.
VENDOR EXHIBIT of products and services will provide valuable support
services and software information to your computer software testing
efforts.
NETWORKING:
Birds-of-a-Feather Sessions allow you to meet and network with the
speakers and other conference attendees, and discuss areas of mutual
interest.
Lunch Discussion Groups will facilitate the exploration of common interest
topics among the participants.
FOR INFORMATION:
Regular Mail: USPDI, 612 Ethan Allen Avenue, Suite 100; Takoma Park,
MD 20912-5400 (USA)
Phone: (+1) 301-270-1033
Fax: (+1) 301-270-1040
E-mail: admin@uspdi.org (Subject: TCS2001)
MARK YOUR CALENDAR FOR THE 18th ANNUAL EVENT!
Complete program information is available on the web at
http://www.uspdi.org/conference
Detailed printed brochure is available, and can be requested:
from USPDI (see above),
or the Web at http://www.uspdi.org/conference/brochure.html
You can also register on-line at:
http://www.uspdi.org/conference/register.html
*****
------------------------------
Date: Thu, 12 Apr 2001 16:41:32 -0500
From: Robert Lowe <Robert.H.Lowe@X-no.spam-X.lawrence.edu>
Subject: Can File::Find selectively search subdirs?
Message-Id: <3AD6210C.E90196B4@X-no.spam-X.lawrence.edu>
Hi!
I'd like to make File::Find only search one particular subdirectory
of a lot of top-level directories, but I don't seem to be finding
the trick. For example, say I want to search every user's home
directory for a .netscape directory, and then find every file
matching /^(li|)prefs.js$/ in that subdirectory. All this without
going into other directories under the home directories. Any ideas?
Two separate subroutines, one with File::Find::prune set and the
other not perhaps? Any simpler way?
TIA,
Robert
------------------------------
Date: 12 Apr 2001 15:28:16 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: Can File::Find selectively search subdirs?
Message-Id: <m14rvtpxbz.fsf@halfdome.holdit.com>
>>>>> "Robert" == Robert Lowe <Robert.H.Lowe@X-no.spam-X.lawrence.edu> writes:
Robert> I'd like to make File::Find only search one particular subdirectory
Robert> of a lot of top-level directories, but I don't seem to be finding
Robert> the trick. For example, say I want to search every user's home
Robert> directory for a .netscape directory, and then find every file
Robert> matching /^(li|)prefs.js$/ in that subdirectory. All this without
Robert> going into other directories under the home directories. Any ideas?
Robert> Two separate subroutines, one with File::Find::prune set and the
Robert> other not perhaps? Any simpler way?
Well, "every user's home directory" with a ".netscape" directory is
fetched from getpwent like so:
my @dirs = grep -d "$_/.netscape", do {
my %list;
my @item;
$list{$item[7]}++ while @item = getpwent;
keys %list;
};
Then use @dirs as your starting points for a File::Find.
If you have a different problem, yes, "return $File::Find::prune = 1;"
can be your friend. But you'll first have to give me a different
problem to solve, because this one I'd solve this way. :)
print "Just another Perl hacker,";
--
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: 12 Apr 2001 15:38:29 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: Can File::Find selectively search subdirs?
Message-Id: <m1vgo9oiai.fsf@halfdome.holdit.com>
>>>>> "Randal" == Randal L Schwartz <merlyn@stonehenge.com> writes:
Randal> Well, "every user's home directory" with a ".netscape" directory is
Randal> fetched from getpwent like so:
Randal> my @dirs = grep -d "$_/.netscape", do {
Randal> my %list;
Randal> my @item;
Randal> $list{$item[7]}++ while @item = getpwent;
Randal> keys %list;
Randal> };
Randal> Then use @dirs as your starting points for a File::Find.
Oops... not quite. That's all the homedirs that have a .netscape subdir.
To make it useful for File::Find, you gotta do this instead:
my @dirs = grep -d, do {
my %list;
my @item;
$list{$item[7]}++ while @item = getpwent;
map "$_/.netscape", keys %list;
};
--
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: Thu, 12 Apr 2001 22:27:12 GMT
From: mjd@plover.com (Mark Jason Dominus)
Subject: Re: Can File::Find selectively search subdirs?
Message-Id: <3ad62bc0.256e$2b4@news.op.net>
In article <3AD6210C.E90196B4@X-no.spam-X.lawrence.edu>,
Robert Lowe <Robert.H.Lowe@X-no.spam-X.lawrence.edu> wrote:
>I'd like to make File::Find only search one particular subdirectory
>of a lot of top-level directories...
>For example, say I want to search every user's home
>directory for a .netscape directory,
> and then find every file
>matching /^(li|)prefs.js$/ in that subdirectory.
It seems to me that File::Find is the wrong tool here.
I would do something more like this:
while (@data = getpwent) {
my $dir = $data[7]; # home directory
push @files,
grep -e, "$dir/.netscape/prefs.js",
"$dir/.netscape/liprefs.js";
}
--
@P=split//,".URRUU\c8R";@d=split//,"\nrekcah xinU / lreP rehtona tsuJ";sub p{
@p{"r$p","u$p"}=(P,P);pipe"r$p","u$p";++$p;($q*=2)+=$f=!fork;map{$P=$P[$f^ord
($p{$_})&6];$p{$_}=/ ^$P/ix?$P:close$_}keys%p}p;p;p;p;p;map{$p{$_}=~/^[P.]/&&
close$_}%p;wait until$?;map{/^r/&&<$_>}%p;$_=$d[$q];sleep rand(2)if/\S/;print
------------------------------
Date: Fri, 13 Apr 2001 01:25:29 GMT
From: Robert Lowe <Robert.H.Lowe@X-no.spam-X.lawrence.edu>
Subject: Re: Can File::Find selectively search subdirs?
Message-Id: <3AD6559D.613DD97E@X-no.spam-X.lawrence.edu>
"Randal L. Schwartz" wrote:
>
> >>>>> "Randal" == Randal L Schwartz <merlyn@stonehenge.com> writes:
>
> Randal> Well, "every user's home directory" with a ".netscape" directory is
> Randal> fetched from getpwent like so:
>
> Randal> my @dirs = grep -d "$_/.netscape", do {
> Randal> my %list;
> Randal> my @item;
> Randal> $list{$item[7]}++ while @item = getpwent;
> Randal> keys %list;
> Randal> };
>
> Randal> Then use @dirs as your starting points for a File::Find.
>
> Oops... not quite. That's all the homedirs that have a .netscape subdir.
> To make it useful for File::Find, you gotta do this instead:
>
> my @dirs = grep -d, do {
> my %list;
> my @item;
> $list{$item[7]}++ while @item = getpwent;
> map "$_/.netscape", keys %list;
> };
I hadn't thought of this -- and if I had, I'm sure my solution
would not have been as elegant! :)
While this makes good sense for UNIX, what if I also have a
similar problem on a Windows system, where home directories are
X:\group-name\username\ (I believe home directories might only
point to the group folder too)?? I'm not familiar enough with
Perl on Win32 systems to know if/how getpwent might even be
implemented there . If it, or something similiar, can be used
there, then I'm set in both cases. If not, then it seems like
a harder nut to crack, even if only in a platform-independent
manner. It sure seems like it would nice if File::Find could
be told to prune after N levels, rather than just 'yes' or
'no', doesn't it? Maybe I can accomplish this by setting
File::Find::prune=0 until the number of directory separators
(forward or backward slash) in File::Find::dir reaches the
magic number, and then set it to 1 unless I hit on the
desired directory? Or does that still seem like the wrong
approach?
TIA,
Robert
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 686
**************************************
