On 21 February 2015 at 04:29, nicolas <nicolas...@mail.com> wrote:
>
> Global symbol "$CONFIG_FILE" requires explicit package name at vowCons2.pm
> line 18.
> Compilation failed in require at sufpref.pm line 10.
> BEGIN failed--compilation aborted at sufpref.pm line 10.
> Compilation failed in require at ./base.pl line 32.
> BEGIN failed--compilation aborted at ./base.pl line 32.
>
> Should I create CONFIG_FILE directory ?
>
No. The issue ( as I explained in the other mail ) is $CONFIG_FILE is a
variable in this context, and it is previously undefined.
Here is what a more recent version of Perl does with that error:
perl -wE' use strict; print $CONFIG_FILE'
Global symbol "$CONFIG_FILE" requires explicit package name (did you forget
to declare "my $CONFIG_FILE"?) at -e line 1.
Turning on diagnostics will reveal the nature of this error:
perl -Mdiagnostics -wE' use strict; print $CONFIG_FILE'
Global symbol "$CONFIG_FILE" requires explicit package name (did you forget
to declare "my $CONFIG_FILE"?) at -e line 1.
Execution of -e aborted due to compilation errors (#1)
(F) You've said "use strict" or "use strict vars", which indicates
that all variables must either be lexically scoped (using "my" or
"state"),
declared beforehand using "our", or explicitly qualified to say
which package the global variable is in (using "::").
Uncaught exception from user code:
Global symbol "$CONFIG_FILE" requires explicit package name (did
you forget to declare "my $CONFIG_FILE"?) at -e line 1.
Execution of -e aborted due to compilation errors.
So you need to actually set that variable somewhere before you use it.
--
Kent
*KENTNL* - https://metacpan.org/author/KENTNL
