[snip]
Digest::MD5, and tomorrow, I decide that the function isn't going to
be called 'md5_base64' anymore, because I got sick of typing it. From
now on it's going to be 'md5_64'. You now have to go through and fix
your module to make it export the new function name.
That is exactly the point of why I want to dynamically import() it instead of having
sub parent_foo { Parent::parent_foo(@_) }
or the GLOB version of that or whateverfor each one.
because the way I have it now when you change it to md5_64 (or add a new function md5_super_duper or remove md5_base64) I have 0 changes to make in my Module because import() figures out which arguments to add to @EXPORT_OK and give to Digest::MD5->import().
So immediately without updating my module you can
use Parent::Subclass qw(subclas_func md5_64 md5_super_duper);
yes if the md5_sum function is removed
use Parent::Subclass qw(md5_sum);
would break with a "Parent does not export md5_sum()" but so would
use Parent qw(md5_sum);
so thats no big deal (and still would mean 0 changes to my module)
I did not include how I dynamically figure out the args to pas to import import() in my sample code because I had that figured out already and needed to learn how to do the one part I needed. hence the simple example that illustrated how I was tryting to acheive what I'd described.
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
