On Fri, Aug 31, 2001 at 04:08:18PM -0700, Dave Storrs wrote:
> How would this handle code and/or packages that are generated at run
> time? Or would that be another caveat?
If a piece of code depends on a package it generates itself... doesn't
sound like much of a dependency.
Anyhow, RFC 289 (v
How would this handle code and/or packages that are generated at run
time? Or would that be another caveat?
Dave
On Fri, 31 Aug 2001, Steve Simmons wrote:
> > Perl6 should ship with a simple utility that shows all modules a program
> > uses, and all modules those modules use.
>
> Presumably
> Perl6 should ship with a simple utility that shows all modules a program
> uses, and all modules those modules use.
Presumably with the caveat that no usage list can be generated for any
missing modules.
On Mon, Sep 25, 2000 at 02:56:20AM -0500, Curtis Jewell wrote:
> Or would this tool be restricted to compile-time dependencies only?
I see no problem restricting dependency graphs to compile-time
dependencies.
Z.
r 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 PROTECT
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
