Re: Understanding errors

To your general question: put in use diagnostics; at the top of your script to get nice, long, explanatory error messages. Great help when starting out.

Other advice: put use strict up there ALWAYS, and add a -w to the command line, the latter especially when developing.

As to the specific error ... it SOUNDS like the problem's in the module code ... but I can't comment on that directly. Check to make sure you typed the code in correctly.

Also: what is line #4 (the one reported as containing the error ?). Knowing that can go a long way to helping out with this one.

Philosophy can be made out of anything. Or less -- Jerry A. Fodor

Comment on Re: Understanding errors Select or Download Code

Replies are listed 'Best First'.
Re: Re: Understanding errors by carson894 (Initiate) on Feb 28, 2001 at 02:14 UTC
The "use Diagnostics;" sure does give me a lot more info. Thanks.<PB> Line 4 is:<PB> `if( Win32::AdminMisc::GetGroups( $Machine, GROUP_TYPE_GLOBAL, \@List ) + )` [download]	[reply] [d/l]