> So I'd like to propose the following for inclusion.
>
> Metric: consistent_newlines
>
> The distribution is awarded a point IF for ALL text
> files within the distribution EACH file contains
> EITHER exclusively unix newlines OR exclusively
> Win32 newlines.
In addition, I'd be happy to cook
I have never actually had an opportunity to practice
this, but I've always felt that the most obvious way
to combine test-driven development with pair
programming was to have one person write test code
while the other person writes application code.
Presumably they might change roles periodically,
I just found http://search.cpan.org/dist/Test-Strict,
which was written by one of my co-workers. Among
other cool things, it has a C function
which does the same thing. It still uses backticks
and redirection which may not be too portable, but it
will suit my needs. Still, a C function
seems lik
Putting aside the argument that most logic should be
in libraries and not scripts, what is the best
practice for writing test cases to verify that your
Perl scripts compile? My quick and dirty solution is
something like:
use Test::More tests => 1;
chomp (my $output = `perl -c $script 2>&1`);
i
> If you want to equip programmers to talk to
> management, donât
> forget to give them this link:
> http://www.martinfowler.com/bliki/TechnicalDebt.html
Thanks for this. I've heard the term "Technical Debt"
a few times lately and I really like it. Unlike a
financial debt however, there is a p
> If you're talking to a bunch of perl mongers I
> recommend talking about
> perl instead of spouting management-speak. The
> Republic Of Ireland has
> nothing to do with perl programming.
I can appreciate that, but I have to believe that no
one likes writing crappy code. And more so, no one
l
> >By lowering maintenance costs via quality control,
> managers can
> >avoid (or at least postpone) having to scrap their
> entire system
> >and rebuild from scratch in India.
>
> I think this is a bit of a stretch.
I'm in the middle of one such situation. I have
inherited a 500k line legacy sy
Hello everyone-
I'm working on a presentation of Perl::Critic for the
local perlmongers group. As part of the presentation,
I would like to make some comments about the current
industry trends around software quality. Basically,
I'd like to assert that there is a growing emphasis on
software qua
Randy Kobes distributes Win32 PPMs for some of the
modules that ActiveState doesn't provide. It is not
entirely automated, so the latest code isn't always
available. But Randy is very helpful if there's
anything you want to see.
http://theoryx5.uwinnipeg.ca/ppms/
-Jeff
> > I'm somewhat new to
Greetings,
I've noticed that CPAN authors use a variety of
techniques to manipulate the run-time environment in
their test scripts. Usually, it involves changing
directories and/or altering @INC. This one seem pretty
popular:
BEGIN {
if($ENV{PERL_CORE}) { #What is "PERL_CORE"?
10 matches
Mail list logo
