This begs a question - How would this be implemented, knowing that at least
some MAJOR modules have what I call "run-time" dependencies, which are very
easy to do with Perl?
For example, what would this option think of DBI, for example, with it
loading DBD's based on subroutine parameters?
Or, say, from my own code, which does not REQUIRE Filesys::DiskSpace to
continue, but if it can use it, it does... is that really a dependency, and
how would the proposed tool/option know this?
my ($fs_type, $fs_desc, $kb_used, $kb_avail, $inodes_used, $inodes_avail);
eval 'use Filesys::DiskSpace; ($fs_type, $fs_desc, $kb_used, $kb_avail,
$inodes_used, $inodes_avail) = df "/home/devel/"';
if (!$@) {
if ($kb_avail < 20 * 1024) { # 20 MB left is our "warning signal"
$self->misdb_error("Unexpected connection problem: Low disk space.
Contact web site maintainer.");
return 1;
}
}
Or would this tool be restricted to compile-time dependencies only?
--
Curtis Jewell http://www.geocities.com/curtis_whalen/ [EMAIL PROTECTED]
http://new-york.utica.mission.net/ [EMAIL PROTECTED]
No matter where we fall or where we land | [EMAIL PROTECTED]
I believe we're part of a master plan (from "Wonderland" on the Ptm2K OMPS)
----- Original Message -----
From: "Perl6 RFC Librarian" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, September 25, 2000 01:02
Subject: RFC 289 (v1) Generate module dependencies easily
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITLE
>
> Generate module dependencies easily
>
> =head1 VERSION
>
> Maintainer: Adam Turoff <[EMAIL PROTECTED]>
> Date: 24 Sep 2000
> Mailing List: [EMAIL PROTECTED]
> Number: 289
> Version: 1
> Status: Developing
>
> =head1 ABSTRACT
>
> Perl6 should ship with a simple utility that shows all modules a program
> uses, and all modules those modules use.
>
> =head1 DESCRIPTION
>
> Tom Christiansen proposed this in his perl6storm message:
>
> =item perl6storm #0043
>
> Write something that spits out module dependencies. Like makedep.
> A tool that sources but doesn't run? a program/module then spits
> out %INC might suffice. Can we autobundle with CPAN tricks?
>
> This feature will be useful for quite a number of uses, including bundling
> modules for distribution, and generating snapshots of large Perl programs.
>
> =head1 IMPLEMENTATION
>
> This feature is probably best implemented through a standard module used
as
> a compiler backend.
>
> =head1 REFERENCES
>
> None.
