Re: Best way to dynamically use a .pm?

[Tux]

Why put the data in .pm files? Can't it be controlled by data structures in some readable way, like JSON or YAML? Does it need to include code? If parameters in the config files can control program flow in the module, I'd say stick to config files and not dynamic modules. An alternative to JSON of YAML might be to look at any of the plethora of Config:: modules on CPAN.

Then there is the long forgotten support for files in the do keyword:

$ cat honda.pl
#!perl

print STDERR "Using Honda\n";
sub honda { print "Honda rulez\n"; }

1;
$ perl -wE'do "honda.pl";say 2;honda()'
Using Honda
2
Honda rulez
$

do does accept variables :)

[TJPride]

Queries, templates, and the data interface between the two can vary widely between dealers, with no way to predict in advance. The best way to handle this is custom-modified subs, as far as I can tell. Essentially, the same .pm only in many different flavors. Maybe this isn't the best approach, but it seems to be working - I was only really concerned with efficiency, now that it'll have to be done for large numbers of transactions rather than just a few data imports.