5.8 docs talks about Defining-multiple-constants-at-once and 5.6 docs does not. You are using version 5.6 and that could be the problem.

artist

use constant (
   VALID => 1,
   INVALID => 2,
   ERROR => 0,
);
[download]

According to the docs, for multiple declarations you use a hashref.. Their example, copy-pasted:

    use constant {
        SEC   => 0,
        MIN   => 1,
        HOUR  => 2,
        MDAY  => 3,
        MON   => 4,
        YEAR  => 5,
        WDAY  => 6,
        YDAY  => 7,
        ISDST => 8,
    };
[download]


So I don't think that's it. I'll try your suggestion anyway though.

Edit: Just tried it, none of the constants worked, even those that did previously. (They work inside the module they were declared in, but won't export.)



---




My code doesn't have bugs, it just develops random features.

Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

our @EXPORT_OK = @{ $EXPORT_TAGS{'all'} };
[download]

Ok, the code now reads:


package MyPackage;
use Data::Dumper;
use 5.006;
#use Data::Validate::OO::Tests;
use Tests;

#use constant {
#   VALID => 1,
#   INVALID => 2,
#   ERROR => 0,
#   };
use constant VALID => 1;
use constant INVALID => 2;
use constant ERROR => 0;
use strict;
use warnings;

require Exporter;
use AutoLoader qw(AUTOLOAD);

our @ISA = qw(Exporter);

our %EXPORT_TAGS = (
   'all' => ['VALID','INVALID','ERROR'],
   'codes' => ['VALID','INVALID','ERROR'],
);

our @EXPORT_OK = @{ $EXPORT_TAGS{'all'} };

our @EXPORT = qw();  #Intentionally left blank

our $VERSION = v0.0.1;
[download]

And I'm testing it with this:

use MyPackage qw(:all);
use Data::Dumper;
use strict;
use warnings;

print STDOUT VALID;
[download]



It still yields the same error...



---




My code doesn't have bugs, it just develops random features.

Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

I took your example exactly Flame, except that I commented out the "use Tests" (I don't have that module) and the "use Autoloader" (it causes errors if the package isn't installed, and I was testing it from the current directory). The example worked with no problem.

(It also works with MyPackage::VALID, but I wouldn't call that an import.)

I'm wondering if perhaps you aren't testing the package you think you are. Is the right copy of MyPackage.pm in your @INC path first? Did you reinstall the package after making the changes?

use MyPackage qw(:all);
use Data::Dumper;
use strict;
use warnings;

print STDOUT MyPackage::VALID;
[download]

Untested.

John J Reiser
newrisedesigns.com

package MyPackage;
use 5.006;
use strict;
use warnings;

use Data::Dumper;
use constant VALID => 1;
use constant INVALID => 2;
use constant ERROR => 0;

use base qw(Exporter);

our @EXPORT_OK = qw(VALID INVALID ERROR);

our %EXPORT_TAGS = (
   'all' => \@EXPORT_OK,
   'codes' => [ qw(VALID INVALID ERROR)],
);

our @EXPORT;  #Intentionally left blank

our $VERSION = v0.0.1;
[download]

Makeshifts last the longest.

Hmm, that didn't seem to work at first... but I think I solved my problem. I wasn't really using package MyPackage... the package was Data::Validate::OO and I was using "use OO" because I was testing from within the same dir as Data::Validate::OO was being written in... so... it looks like it was failing to call export properly... I'm now using 'use lib' to use the full package name and it works again.



---




My code doesn't have bugs, it just develops random features.

Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

Well, that explains it. use Foo does this:

BEGIN {
    require Foo;
    Foo->import;
}
[download]

If you use OO, require will find your module, but of course the module will still create the Data::Validator::OO package and not an OO package, causing the following OO->import to fail (silently).

Makeshifts last the longest.