DBI
module and I hadn't written much with modules.
jacoby@oz:~/lib$ ls -l SecGenTools.pm
-rw------- 1 jacoby jacoby 60575 2010-01-26 15:25 SecGenTools.pm
jacoby@oz:~/lib$ wc SecGenTools.pm
2175 8253 60575 SecGenTools.pm
jacoby@oz:~/lib$ grep 'sub ' SecGenTools.pm | wc -l
96
jacoby@oz:~/lib$
Now, I'd love to refactor, break it apart into little pieces, but I'm at a loss about how.
It would be fairly easy to break out
SecGenTools::FormTools
and SecGenTools::RequestTools
and the like. That makes seven kinds of sense. The problem is that I don't have use SecGenTools::FormTools ;
in the existing code, I just have use SecGenTools::FormTools ;
I could imagine line after line like this.- package Dumb ;
- use strict ;
- use warnings ;
- use Dumb::Dumber ;
- use Exporter qw(import) ;
- our %EXPORT_TAGS = (
- 'all' => [ qw( my_function ) ] ,
- ) ;
- sub dumb_function {
- return Dumb::Dumber::dumb_function( @_ ) ;
- }
- 1 ;
But that seems fragile and quite stupid.
Is there any way to seemlessly export the functions of
Dumb::Dumber
from Dumb
without explicitly writing wrapper functions within Dumb
? Or am I doomed?
No comments:
Post a Comment