> In all sincerity, your Lingua::Romana::Perligata module is a good
> example. Although not many people may desire to code perl in Latin,
> it is certainly conceivable that modules similar to Perligata may
> allow programming perl in a variety of languages native to the
> progr
I haven't (and won't) have time to go into this in detail :-(
I feel that this proposal is solving the wrong problem. The issue is
that the original Forest and Frog (or DBI and DBI::st) classes are not
*designed* for user-definable Frogs (DBI::st's). If that functionality
is widely needed, the Fo
> [From DBI->connect()]
>
> # XXX this is inelegant but practical in the short term, sigh.
> if ($installed_rootclass{$class}) {
> $dbh->{RootClass} = $class;
> bless $dbh => $class.'::db';
> my ($outer, $inner) = DBI::_handles($dbh);
> bless $inner => $cla
On Mon, Sep 18, 2000 at 05:49:28AM -, Perl6 RFC Librarian wrote:
> Here's where the problem lies. Even though we now have a subclass
> of Frog, the Forest class is still referencing the original Frog
> class and not Frog::Japanese.
The DBI has this very problem! DBI->connect() returns DBI::
