I should add that I'll probably have to revise doc/configuration.pod a
bit to impose a rule that Perl 5 %Config may only be 'use-d' in
init::defaults.  I'll also have to revise the documentation for
Parrot::Configure::Data::keys() to include a caution about avoiding the
'p5Config_' elements.

OTOH, perhaps it might be best to stash all those p5Config elements in a
different part/level of the Parrot::Configure object, so that they can
not possibly be accessed by methods such as keys().  What do people think?


Reply via email to