So, I took your suggestion and wrote the following subroutine. Much of it is just the process of comparing the module's path to the object being called to determine the module name. It works well if I put it in a script; however, when I put it in a module (such that it runs on import), running a script that calls the module essentially fork bombs my machine. Any suggestions on possible workarounds? When I get a chance tonight, I'll look at the B::Xref source and see if I can figure something out. Thanks.
sub check_conflicts {
my @xref_out = `perl -MO=Xref,-r $0 2> /dev/null`;
@xref_out = grep { /ARGV/ } @xref_out;
my %conflicts;
for (@xref_out) {
my ($module_path, $object ) = split /\s/;
$module_path =~ s|/|::|g;
my @object_path = split /::/, $object;
for (0 .. $#object_path) {
my $module_name = join "::", @object_path[0..$_];
if ($module_path =~ /$module_name\.pm/) {
$conflicts{$module_name} = 1;
last;
}
};
}
say $_ for keys %conflicts;
}
-
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.
|