qq,
Thanks for taking to time to provide that framework. That is what I was looking for to my overall design question. The one other question I have is about self determination of all the available processors. I planned on doing something similar to the following code, but I need to determine the base class versus just matching on the name of the object:
foreach $symname (sort keys %main::) {
#print "$_\n" if /^ybcp/;
if ( $symname =~ /^ybcp/ ) {
local *sym = $main::{$symname};
$$sym->init();
#print "\$$symname\n" if defined $sym;
}
}
With loops like this in my driver script, I should be able to simply add a new use statement for new processors.
Also... Just to wrap up my thoughts on my original issue. I was confused by my Perl book's explanation of the Exporter implementation. I thought it was necessary to add methods to the Exporter to make them accessible, but I now realize that it meant accessible without the module:: syntax.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.