Since perl6 will/should have a new Configure methodology[1] there
could be a registry (hate that word) of all available function
calls[2], developed during the build processes. Then the core would be
able to infer a 'use' command.

<chaim>

[1] Where is the perl6-configure list? Did anyone request one?
[2] perhaps extracted from the replacement of @EXPORT_*

>>>>> "NT" == Nathan Torkington <[EMAIL PROTECTED]> writes:

NT> Moving things to modules (a) does little for the size of Perl, and (b)
NT> promotes Pythonization of the language (i.e., all programs begin with
NT> 20 lines of `load this module, load that module, load the other
NT> module').  Your criteria for moving to a module can't simply be
NT> whether it's a system call or not, you must use something that takes
NT> into account the hindrance and the payoff.

-- 
Chaim Frenkel                                        Nonlinear Knowledge, Inc.
[EMAIL PROTECTED]                                               +1-718-236-0183

Reply via email to