comment on

One idea would be to make a snapshot of %INC when compile time ends. If an entry is in the snapshot, the module was use()d, otherwise it was require()d.

For instance:

CHECK {
    my %snap = %INC;

    sub report {
        for ( keys %INC ) {
            my $ans = $snap{ $_} ? 'use()d' : 'require()d';
            print "$_ was $ans\n";
        }
    }
}
[download]

Here, report() simply prints a list with each module's status. A more elaborate version could return the status of a module that is passed in.

Of course, %INC can be manipulated in every which way, so the method isn't fool-proof. It makes up for that with simplicity.

Update:
Another possible drawback of this approach is that the module that implements it must itself be use()d and can't be loaded at run time. (It would be too late to run the CHECK block.) That may be true for other solutions also.

Anno

In reply to Re: Was a module use'd or require'd? by Anno
in thread Was a module use'd or require'd? by Ovid

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks