perlunit-users — PerlUnit users' mailing list

[Perlunit-users] Testing module validity with test::Unit

[Dmitry D. <dd...@ic...>]

Hello All!

 From the Test::More documentation I learned about use_ok() and 
require_ok() test functions. They recommend to use them as follows:

   BEGIN { use_ok('Some::Module') }
   BEGIN { ...some code that depends on the use... }

In the case of failure to 'use' some module test will report it. Is 
there any way (or need?) to do something similar with Test::Unit? Say, I 
want to test my class methods, but the whole module is broken. I will 
get standard perl compile error in that case?

Regards,
Dmitry.

[Perlunit-users] Re: test-unit-0.24 Installation

[Adam S. <ad...@sp...>]

[Please send queries to the perlunit-users mailing list.]

Jitendra Barlinge (jx...@ac...) wrote:
> I am trying to install Test-Unit-0.24 on windows NT 6.0 sp 6a  having perl 
> v5.6.1 build 629
> 
> downloaded and copied the whole tree in a folder then copied following:
> Devel\Symdump.pm
> Error.pm
> Class\Inner.pm
> base.pm
> 
> then I did the following
> 
> perl makefile.pl
> namke
> namke test
> 
> when I do "namke test" it causes a crash on each test except try_examples
> 
> I get following on the STDOUT
> 
> Failed 3/3 test scripts, 0.00% okay. 1/4 subtests failed, 75.00% okay.
> name : fatal error U1077: d:\perl\bin\perl.exe : return code '0xff'
> stop
> 
> 
> am I doing something wrong?

Yes, you should follow the

  perl Makefile.PL
  make
  make test
  make install

procedure for each individual module, rather than copying .pm files
around manually.

If at any stage, `make test' fails, run it as

  make test TEST_VERBOSE=y

to see which test failed.

[Perlunit-users] New maintainer required

[Adam S. <ad...@sp...>]

As just mentioned on perlunit-users, my new job doesn't require the
use of PerlUnit so I basically have next to no time to maintain it :-(
So if someone would like to take over, please get in touch - I'd be
really grateful.

I'll still hang around to answer questions, since the code base is not
the easiest thing to understand.  I never ignore questions (and in
fact still have a small backlog to get through), but responses to
questions will invariably take a while though, unless you want to pay
me for support, in which case I can escalate the priority.

Adam

-- 
## Adam Spiers ## musician & hacker ## me...@ad... ## http://tigerpig.org
$@=>$_=q^*{$Just =bless{},'$another ';"\$Perl \::$hacker,"}=sub{print$%[$.++];$
},eval join+v45.62,(q)$q ))x v54^,s.(?<=\$)\w*[\s,].f if+push@%,$&.sixmegs,eval

Re: [Perlunit-users] Patch to fix assert_deep_equals() on circular structures.

[Adam S. <ad...@sp...>]

Francis J. Lacoste (fra...@co...) wrote:
> (I'm sending this here, altough the mailing lists seems quite dormant
> looking from the archives on SF.)

They are, I'm afraid.  My new job doesn't require the use of PerlUnit
so I basically have next to no time to maintain it :-( If someone
would like to take over, I'd be really grateful.  I'll still hang
around to answer questions, although the response time will usually be
long.  (Unless you want to pay me for support, in which case I can
escalate the priority.)

> I'm using the perl unit framework in the Lire log analyser and we have
> objects which have circular references. Unfortunately,
> assert_deep_equals() will enter infinite recursion on such structure.
> 
> I'm attaching the a patch (apply using -p1) which fixes this. The patch
> also adds the proper check to the AssertTest unit tests.

This is great; thanks very much indeed.  I'll apply it to CVS when I
get a spare moment, and make a new release.  Maybe this weekend.

[Perlunit-users] Patch to fix assert_deep_equals() on circular structures.

[Francis J. L. <fra...@co...>]

Hello everyone,

(I'm sending this here, altough the mailing lists seems quite dormant
looking from the archives on SF.)

I'm using the perl unit framework in the Lire log analyser and we have
objects which have circular references. Unfortunately,
assert_deep_equals() will enter infinite recursion on such structure.

I'm attaching the a patch (apply using -p1) which fixes this. The patch
also adds the proper check to the AssertTest unit tests.

(This patch was also uploaded to the SF tracker).

-- 
Francis J. Lacoste
fr...@Co...

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

Thanks for your help Danny. I will check on gmake.

I didn't have any trouble installing the prerequisite classes using PPM, 
but when i tried to install them using CPAN, then they ran into the same 
make problems i hit with Test::Unit.

Anyway, i just copied all the PM files into my site-lib directory by hand 
and i've been using Test::Unit without a problem. TestRunner.pl and all 
work fine.

Thanks again for everyone's help.

Bret

At 03:50 PM 1/3/2003, Danny Faught wrote:
>Bret Pettichord wrote:
>>I seem to have a problem with make. It fails with the same message with 
>>any perl package. I've tried a couple different versions, to no avail. I 
>>also tried installing cygwin perl, but that didn't help.
>>I can use PPM to install other modules, but not Test::Unit.
>
>I was unable to install Test::Unit using the CPAN module because I needed 
>to install the Class::Inner prerequisite, and the tests for Test::Inner 
>fail on my machine.  Do you already have Class::Inner installed?
>
>I installed Class::Inner from the tarball by hand (using gmake), and 
>noticed that the tests pass if I call them directly, without using 
>Test::Harness.
>
>With Class::Inner installed, I was able to install Test::Unit using the 
>CPAN module. The make error you see looks like a fundamental configuration 
>problem.  Are you using a Cygwin version of gmake?  BTW, I'm using Cygwin 
>(not sure how to tell what version) on Windows NT 4.0, using the Cygwin 
>Perl build, v5.6.1.
>
>I also just tried a CPAN install on a similar configuration except it's 
>Windows 2000, and got the same results.
>
>>It is possible to install this by hand?
>
>I would imagine, if you know what files need to go where.
>--
>Danny Faught
>Tejas Software Consulting
>http://www.tejasconsulting.com

_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

Re: [Perlunit-users] perl unit availability

[Danny F. <fa...@te...>]

Bret Pettichord wrote:
> I seem to have a problem with make. It fails with the same message with 
> any perl package. I've tried a couple different versions, to no avail. I 
> also tried installing cygwin perl, but that didn't help.
> 
> I can use PPM to install other modules, but not Test::Unit.

I was unable to install Test::Unit using the CPAN module because I 
needed to install the Class::Inner prerequisite, and the tests for 
Test::Inner fail on my machine.  Do you already have Class::Inner installed?

I installed Class::Inner from the tarball by hand (using gmake), and 
noticed that the tests pass if I call them directly, without using 
Test::Harness.

With Class::Inner installed, I was able to install Test::Unit using the 
CPAN module. The make error you see looks like a fundamental 
configuration problem.  Are you using a Cygwin version of gmake?  BTW, 
I'm using Cygwin (not sure how to tell what version) on Windows NT 4.0, 
using the Cygwin Perl build, v5.6.1.

I also just tried a CPAN install on a similar configuration except it's 
Windows 2000, and got the same results.

> It is possible to install this by hand?

I would imagine, if you know what files need to go where.
-- 
Danny Faught
Tejas Software Consulting
http://www.tejasconsulting.com

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

At 01:52 PM 1/3/2003, chromatic wrote:
>On Friday 03 January 2003 11:38, Bret Pettichord wrote:
>
> > I seem to have a problem with make. It fails with the same message with any
> > perl package. I've tried a couple different versions, to no avail. I also
> > tried installing cygwin perl, but that didn't help.
>
>Have you tried nmake?  It should be installed with VS, but it's been a long
>time since I looked.

No. I don't have VS. And it doesn't seem to be part of cygwin.

_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

Re: [Perlunit-users] perl unit availability

[chromatic <chr...@wg...>]

On Friday 03 January 2003 11:38, Bret Pettichord wrote:

> I seem to have a problem with make. It fails with the same message with any
> perl package. I've tried a couple different versions, to no avail. I also
> tried installing cygwin perl, but that didn't help.

Have you tried nmake?  It should be installed with VS, but it's been a long 
time since I looked.

-- c

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

I seem to have a problem with make. It fails with the same message with any 
perl package. I've tried a couple different versions, to no avail. I also 
tried installing cygwin perl, but that didn't help.

I can use PPM to install other modules, but not Test::Unit.

It is possible to install this by hand?


_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

Re: [Perlunit-users] perl unit availability

[Danny F. <fa...@te...>]

Bret Pettichord wrote:
> I don't have Cygwin's perl installed. Based on your comments, that 
> sounds like a good thing.

I don't fully understand the impact of mixing native tools and Cygwin 
tools, and I sometimes have trouble when I do this.  If you don't have a 
strong grasp of Cygwin either, then I strongly recommend that you use 
the Cygwin build of Perl in a Cygwin environment, or otherwise use a DOS 
shell when interacting with ActiveState Perl.

I have both installed.
-- 
Danny Faught
Tejas Software Consulting
http://www.tejasconsulting.com

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

At 09:40 PM 1/2/2003, Phlip wrote:
> > In the meantime, i'll figure out how to install it manually. I'm using
> > Perl5.8 and the PDK.

I've gone back to Perl5.6

>Install Cygwin to get tar and gzip. (Unfortunately you will also get a Perl -
>use this one only if you comprehend Cygwin's paths, which is unlikely.)

I already had these installed.

>Install either VC++ or Cygwin's g++.

I added this. Is this really necessary? As there C++ code in Test::Unit?

>Expose them to "perl Makefile.PL".

OK. I still get the makefile error that i got before.

$ make
Makefile:746: *** missing separator.  Stop.

This is the version i am using:
$ make -v
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for i686-pc-cygwin

>If you build for Cygwin's perl, you'l need to move the Test from one folder
>site-packages to another.

I don't have Cygwin's perl installed. Based on your comments, that sounds 
like a good thing.



_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

[Perlunit-users] Re: Test::Unit

[Bret P. <br...@pe...>]

At 09:21 AM 1/3/2003, Danny Faught wrote:
>Perhaps the CPAN module works under ActiveState Perl.  When it does work, 
>it's very nice.  "perl -MCPAN -e shell" and then "install 
>Test::Unit".  It'll go get it and install it.

I tried this and got the following error.

Checking if your kit is complete...
Looks good
Writing Makefile for Test::Unit
     -- OK
Running make test
    test -- NOT OK
Running make install
install: too few arguments
Try `install --help' for more information.
    install  -- NOT OK

I'm presuming that this is due to the same make problem i mentioned previously.

>Hopefully, you're not copying the installed files.

Well, i did try this. But i've deleted them afterwards. Hope i didn't 
bollux things.

>At least get the tarball from cpan.org and do a "make install".

As mentioned in previous email, this won't work for me.

I'm out of ideas for how to install it.

Bret


_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

At 05:19 AM 1/3/2003, Adam Spiers wrote:
> > >Should i go back to perl 5.6?
> >
> > Well, i tried this. PPM says that Test-Unit is now available, but i still
> > can't seem to install it with PPM successfully.
>
>What goes wrong?

The first thing that goes wrong is a file not found error. I examined the 
PPD file (which is just xml) and found that it included a pathname to 
non-existant tarball. So i made my own PPD file that pointed to my copy of 
the tarball. And i tried again. That time it SAID that it installed it, but 
none of the PM files were in the right places. So i gave up on that strategy.

I'm going to try to get make working, as Phlip suggested.

Bret

P.S. I am a professional tester. This sometimes makes me rather curt when 
reporting bugs. I'm happy to provide more info if its helpful. In this 
case, i'm still getting my bearings on what is interesting information. And 
i do appreciate the effort you all have made.



_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

Re: [Perlunit-users] perl unit availability

[Adam S. <ad...@sp...>]

Bret Pettichord (br...@pe...) wrote:
> I haven't used perl in a while and i've decided that i want to use a junit 
> style test harness now that i'm going back to it.
> 
> Reading c2.com and the discussion here makes me think that test-unit must 
> be the definitive package for this. Thus i'm confused as to why it isn't 
> included in activestate's ppm repostitories. Any suggestions for why this 
> is so?

Probably because noone has tried running it under ActiveState before
(or maybe they did, but kept it to themselves).  I can't remember
exactly.  Is there any reference to Win32 in the archives for this
list or perlunit-devel?

> I've been able to install all the prerequisites using PPM, but, like i 
> said, Test-Unit isn't in the default repositories. I did find a copy of 
> Test-Unit.PPM but when i tried to install it with PPM, i got this error: 
> Error: no suitable installation target found for package Test-Unit. The 
> problem seems to be that i'm using Perl 5.8.
> 
> I did try a manual install, but ran into this problem.
> 
> >Administrator@LAKATOS /cygdrive/e/Test-Unit-0.24
> >$ make install
> >Makefile:749: *** missing separator.  Stop.
> 
> Line 749 is the third to last line of this section:
> 
> ># --- MakeMaker pm_to_blib section:
> >
> >pm_to_blib: $(TO_INST_PM)
> >        @$(PERLRUNINST) -MExtUtils::Install \
> >        -e "pm_to_blib(qw[ <<pmfiles.dat 
> >],'$(INST_LIB)\auto','$(PM_FILTER)')"
> >
> >$(PM_TO_BLIB)
> ><<
> >                @$(TOUCH) $@
> 
> Should i go back to perl 5.6?

I don't think it's ever been tried properly with anything other than
5.6 although the above is more likely to be an incompatability in the
Cygwin version of make than anything else.

> >Should i go back to perl 5.6?
> 
> Well, i tried this. PPM says that Test-Unit is now available, but i still 
> can't seem to install it with PPM successfully.

What goes wrong?

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

>Should i go back to perl 5.6?

Well, i tried this. PPM says that Test-Unit is now available, but i still 
can't seem to install it with PPM successfully.


_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

Re: [Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

 >In the meantime, i'll figure out how to install it manually. I'm using 
Perl5.8 and the PDK.'

I've been able to install all the prerequisites using PPM, but, like i 
said, Test-Unit isn't in the default repositories. I did find a copy of 
Test-Unit.PPM but when i tried to install it with PPM, i got this error: 
Error: no suitable installation target found for package Test-Unit. The 
problem seems to be that i'm using Perl 5.8.

I did try a manual install, but ran into this problem.

>Administrator@LAKATOS /cygdrive/e/Test-Unit-0.24
>$ make install
>Makefile:749: *** missing separator.  Stop.

Line 749 is the third to last line of this section:

># --- MakeMaker pm_to_blib section:
>
>pm_to_blib: $(TO_INST_PM)
>         @$(PERLRUNINST) -MExtUtils::Install \
>         -e "pm_to_blib(qw[ <<pmfiles.dat 
> ],'$(INST_LIB)\auto','$(PM_FILTER)')"
>
>$(PM_TO_BLIB)
><<
>                 @$(TOUCH) $@

Should i go back to perl 5.6?






_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

[Perlunit-users] perl unit availability

[Bret P. <br...@pe...>]

I haven't used perl in a while and i've decided that i want to use a junit 
style test harness now that i'm going back to it.

Reading c2.com and the discussion here makes me think that test-unit must 
be the definitive package for this. Thus i'm confused as to why it isn't 
included in activestate's ppm repostitories. Any suggestions for why this 
is so?

In the meantime, i'll figure out how to install it manually. I'm using 
Perl5.8 and the PDK.

Bret


_____________________________________
  Bret Pettichord
    Book - www.testinglessons.com
    Hotlist - www.testinghotlist.com
    Consulting - www.pettichord.com

[Perlunit-users] make test fails

[David S. <sa...@MI...>]

All,

Thank you for the work put into Test::Unit.  I tried yesterday to use
the CPAN module to download and install Test::Unit, and the test harness
failed.  The result is after my signature.  It appears that the test
harness code assumes that TestCase::get_matching_methods will always
return the same methods in the same order, which in turn depends on the
order in which hash table elements are returned, which I believe is
undefined.

It would seem that the easy way out of this would be to sort the result
of get_matching_methods, in order to make it deterministic.  Does this
make sense to anyone else?  Thanks,

	David Saff

PERL_DL_NONLAZY=1 /PAG/local/bin/perl "-MExtUtils::Command::MM" "-e"
"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
t/all_tests.......ok
t/assert..........ok
t/try_examples....NOK 1# Test 1 got: 'Suite setup
# ..FSuite teardown
# 
# TIME-SUMMARY
# 
# !!!FAILURES!!!
# Test Results:
# Run: 2, Failures: 1, Errors: 0
# 
# There was 1 failure:
# 1) examples/fail_example.pm:19 - test_fail(fail_example)
# Born to lose ...
# 
# Test was not successful.
# ' (t/try_examples.t at line 103)
#   Expected: 'Suite setup
# .F.Suite teardown
# 
# TIME-SUMMARY
# 
# !!!FAILURES!!!
# Test Results:
# Run: 2, Failures: 1, Errors: 0
# 
# There was 1 failure:
# 1) examples/fail_example.pm:19 - test_fail(fail_example)
# Born to lose ...
# 
# Test was not successful.
# '
t/try_examples....FAILED test 1
	Failed 1/4 tests, 75.00% okay
Failed Test      Stat Wstat Total Fail  Failed  List of Failed
----------------------------------------------------------------------------------------------------
t/try_examples.t                4    1  25.00%  1
Failed 1/3 test scripts, 66.67% okay. 1/83 subtests failed, 98.80% okay.
make: *** [test_dynamic] Error 29

Re: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Adam S. <ad...@sp...>]

Phlip (pl...@sy...) wrote:
> Perlies:
> 
> I like unit tests. My employers like Win32, VC++, and Perl. So here I am
> writing an "acceptance test" rig for our VC++ code, and it calls
> Perl embedded in the C++ code.
> 
> When an assertion fails, such as this one...
> 
>   $self -> assert ($result =~ /LW is god/);

That assertion is potentially buggy.  Please read the
Test::Unit::Assert manpage carefully, and use assert_matches()
instead.

Re: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Phlip <pl...@sy...>]

> Since you're using the full namespace to the method, you don't have to
switch
> packages.

The result compiles, but control flow does not step inside the new version.
Maybe either ptkdb or my embedding rig are interfering. Thanks, but enough
spelunking. Now to add tests!

    http://www.c2.com/cgi/wiki?SheChangeDesignInTheDatabase

--
Phlip
http://www.c2.com/cgi/wiki?RatAndTuyen

Re: [Perlunit-users] Bio-Patch: Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Phlip <pl...@sy...>]

>     my $winFile = $file;
>     $winFile =~ s/\//\\/g;  #  "it's under a Big Dubb'ya"!

Despite my most Perlesque comment, that line's not needed. VC++ accepts /
path separators.

--
Phlip

[Perlunit-users] Bio-Patch: Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Phlip <pl...@sy...>]

> use Test::Unit::Debug;
>  {
>     no warnings 'redefine';
>      package Test::Unit::Debug;
>      *Test::Unit::Debug::debug = sub {
>          my ($package, $filename, $line) = caller();
>          print $out "***************************************that's the
> facts, Jack!\n";
>          print $out @_ if $DEBUG{$package};
>          }
>  }

Trying to get that working exceeded my time box, so I went in for a hack.

Firstly, 'debug' was the wrong method to try to override. I'l eventually
figure out how to perform a hostile override, but for now I went with these
adjustments to the actual source.

First I hack Exception.pm so errors are in this format: path\file(line):

sub stringify {
    my $self = shift;
    my $file = $self->file;
    my $line = $self->line;
    my $message = $self->text || 'Died';
    my $object = $self->object;

    my $winFile = $file;
    $winFile =~ s/\//\\/g;  #  "it's under a Big Dubb'ya"!

    my $str = "$winFile($line)";
    $str .= ': ' . $object->to_string() if $object &&
$object->can('to_string');
    $str .= "\n" . $message;
    return $str;
}

Next, I transmogrify TestRunner::print_failures:

...
    for my $f (@{$result->failures()}) {
        chomp(my $f_to_str = $f);
        $self->_print("\n") if $i++;
        $self->_print("$i) $f_to_str\n");

        use Win32::API::OutputDebugString qw(OutputDebugString);

        OutputDebugString("$f_to_str\n");

        $self->_print("\nAnnotations:\n", $f->object->annotations())
          if $f->object->annotations();
    }
...

The result: I can use tests to drive development in an app written in C++,
using an enourmous test suite written in Perl. All using OneButtonTesting,
without manually navigating back to failure lines.

--
  Phlip
        http://www.greencheese.org/SkeletonCrew
  --  Have a :-) day  --

Re: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Phlip <pl...@sy...>]

> If you're using Perl 5.6 or greater, the warnings pragma can help:
>
> use Test::Unit::Debug;
>
> {
> no warnings 'redefine';
> Test::Unit::Debug::debug = sub { ... };
> }

I thought that needed a star:

use Test::Unit::Debug;
 {
    no warnings 'redefine';
     package Test::Unit::Debug;
     *Test::Unit::Debug::debug = sub {
         my ($package, $filename, $line) = caller();
         print $out "***************************************that's the
facts, Jack!\n";
         print $out @_ if $DEBUG{$package};
         }
 }

Several variations on that produce this:

Variable "%DEBUG" is not imported at c:../ProgrammerTests/SystranTP.pm line
24.
BEGIN not safe after errors--compilation aborted at
c:../ProgrammerTests/Systran
TP.pm line 369.

--
Phlip

http://www.greencheese.org/HatTrick

Re: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' failure time?

[Phlip <pl...@sy...>]

RE: [Perlunit-users] Test-Unit on Win32: OutputDebugString at 'assert' =
failure time?[can we configure this mail server to Reply to the group, =
not the individual? This lets us archive the technical discussions.]=20
  From: Kyle Brost=20
  It seems as though you are doing a lot of work to embed PerlUnit=20
  into your development environment when you don't have to.  There=20
  is another project called CppUnit that would save you a lot of time=20
  and headache.=20

Well, when I got here the shop was absolutely naive to Programmer Tests, =
but they correctly worship their "customer acceptance tests" on the =
server of their product. At the same time I'm too green here to just =
order everyone to comprehend CppUnit's myriad riddles.

So, I downloaded CppUnit, copied their example.cpp into this project, =
and got it to compile >without< CppUnit or all the crud that package =
inexplicably drags along with it. (Legacy of Java legacy of Smalltalk, =
etc.)

I plopped the result here - it's just one header file:

http://www.c2.com/cgi/wiki?VisualCeePlusPlus

It uses the filename(linenumber) -> OutputDebugString trick that lets =
you navigate thru errors or debug traces by tapping <F4> too.

However, this site has a huge investment in Perl scripts to test their =
server, so I am bonding Perl with VC++ so I can then run all those =
scripts thru the GUI instead of the server. I want to see if I can run =
it until smoke rises from it.

But first, their elaborate Perl scripts are screaming for a good =
refactor party first, so...

--=20

Phlip