Re: [Perlunit-devel] Getting up and Running

[Matthew A. <mc...@us...>]

On Thu, Aug 18, 2005 at 03:17:34PM -0400, mah...@va... wrote:

> I am new to the world of XUnit testing and PerlUnit for that manner.

Hello, welcome to a corner of automated-testing-world.

> [...] I run into issues with the 'make test' [...]


> Subroutine make_new_from_error redefined at blib/lib/Test/Unit/Error.pm 
> line 8.

This is odd, because that should be defined exactly once, in its own
package, in the usual way.  A possible cause for this would be %INC
being cleared or otherwise meddled with.  I don't think any Perlunit
code does this, but I've not checked.


Now to the scary stuff.

> Use of reserved word "our" is deprecated at blib/lib/Test/Unit/Assert.pm 
> line 222.

I suspect this is a warning, not an error.  Doing things which are
merely deprecated should not cause a failure.

>         Bareword "our" not allowed while "strict subs" in use at 
> blib/lib/Test/Unit/Assert.pm line 222.
>         Unquoted string "our" may clash with future reserved word at 
> blib/lib/Test/Unit/Assert.pm line 222.

...but it doesn't know the meaning of "our" and we have an error.

If "our" is a word reserved for future use, this suggests you have a
Perl that predates use of "our" to declare global variables.  My Perl
history is a bit fuzzy, but I think that would place it pre-5.005?
But the Makefile.pl requires 5.005 to start, and you say the Perl may
be too new...

Is it possible that you're missing the part of Perl which defines
"our"?  I don't know whether it's defined but I guess 30 minutes
poking about the source would find it.

>         Array found where operator expected at 
> blib/lib/Test/Unit/Assert.pm line 222, at end of line
>                 (Do you need to predeclare our?)
> Global symbol "@Data_Stack" requires explicit package name at 
> blib/lib/Test/Unit/Assert.pm line 222.
>         syntax error at blib/lib/Test/Unit/Assert.pm line 222, near "our 
> @Data_Stack"

This is fallout from interpreting "our" as a string/bareword.


> The first and third error I am not familiar with at all, but with
> the second error I am thinking that perhaps my version of Perl is
> too new. Any help would be appreciated.  Thanks.

If you could tell me the version of Perl you're using ("perl -v" and
"perl -V", note lower- and uppercase "-v"s) it would really help.

It would also be useful to know whether you're running the v0.24
(current release version) or the current CVS head version.

If this is doesn't turn out to be something simple to resolve (is
there a backwards compatibility mode for this new Perl?) then things
will go faster if I can get hold of the same version that you're
using.  Can you tell me where you got it, please?


Matthew  #8-)