Re: CONFIG_FILE

2015-02-20 Thread Brandon McCaig
Nicolas: On Fri, Feb 20, 2015 at 10:29 AM, nicolas wrote: > package vowCons2; > use strict; > use lib::avt; > my $self = {}; > sub new { > my $this = shift; > my ($WORD) = @_; > my $voyConsDef = readConfFile($CONFIG_FILE/vowConsDef); > $self->{'V'} = $$voyConsDef{'V'}; > $self->{'C'} = $$voy

Re: CONFIG_FILE

2015-02-20 Thread Kent Fredric
On 21 February 2015 at 04:29, nicolas 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 lin

Re: "$CONFIG_FILE"

2015-02-20 Thread Kent Fredric
On 21 February 2015 at 02:35, Shawn H Corey wrote: > > > jupiter@jupiter-OptiPlex-755:~/Documents/base-0.50$ ./base.pl -i > > words Global symbol "$CONFIG_FILE" requires explicit package name > > at vowCons2.pm line 18. > > Go to line 18 of vowCons2.pm and change: $CONFIG_FILE > to: $CONFIG_FILE

Re: "$CONFIG_FILE"

2015-02-20 Thread Shawn H Corey
On Fri, 20 Feb 2015 13:38:42 +0100 "nicolas " wrote: > jupiter@jupiter-OptiPlex-755:~/Documents/base-0.50$ ./base.pl -i > words Global symbol "$CONFIG_FILE" requires explicit package name > at vowCons2.pm line 18. Go to line 18 of vowCons2.pm and change: $CONFIG_FILE to: $CONFIG_FILE -- Don'

Re: "$CONFIG_FILE"

2015-02-20 Thread Kent Fredric
On 21 February 2015 at 01:38, nicolas wrote: > Global symbol "$CONFIG_FILE" requires explicit package name at vowCons2.pm > line 18. This file has a syntax error due to $CONFIG_FILE being assigned to in a context where it is not defined. Usually this would mean you need to predeclare it somew