Thanks.
I ask one more moment of assistance to ensure proper structure. Do the 3
groupings below make sense to you? Elements of the "FameHLI::HLI" module
will be regularly used by anyone using the functions in either of the other
two sets. Or would it be more appropriate to have "HLI" and "EXT" fall
below "API" as in "FameHLI::API::HLI"?
Additionally, I am so familiar with "HLI" that the redundancy doesn't bother
me that much, although it looks a little silly. Would "DEF" [FameHLI::DEF]
(as in #DEFine) or "DOTH" (as in '.h') make more sense? Suggestions
appreciated greatly.
I appreciate the time that you have already taken with this.
--daveo
---------------
The components which I wish to deliver fall into 3 categories:
1) #define elements from the '.h';
2) core functions from the C-HLI;
3) extension functions which aid in interacting with the C-HLI.
Since our last discussion I felt compelled to arrange them thusly:
1) FameHLI::HLI
2) FameHLI::API
3) FameHLI::EXT
A sample program might call:
;#======================
use FameHLI::API;
use FameHLI::HLI;
use FameHLI::EXT;
my $rc = FameHLI::API::Cfmini();
printf("The initialization call said '%s'\n",
$FameHLI::EXT::ErrDesc($rc));
printf("If you really need to know, DAILY is '%d'\n",
FameHLI::HLI::HDAILY);
;#======================
