Thanks to all of the on, and off-list feedback I've received over the last month, I've realized I've been missing out on quite a bit.
I tend to read past the finer points that people refer to. For instance... dispatch tables. It is hard for me to wrap my head around how immensely useful such subtle things can be! I've been reading both the Cookbook and HOP _leisurely_ (as a lot of it is still above me), but things are starting to fall into place. For instance... even though most of my code is object oriented, I feel that there are huge advantages to allowing subs to be passed in as arguments (to nearly all methods). As soon as I realized but a subset of potential the dispatch table has, I know I can command and control my entire project from one spot if the argument handling is done properly. My question is, is if it is common practise to use named parameters for incoming arguments to functions/methods. Whether it is or isn't common practise, is it recommended that a project should keep consistent with ALL methods/functions in this regard whichever way one decides? I'm tired of trying to pop/shift error check the way I have been. It's a nightmare when I want to add a new argument to an API, as it immediately causes great (oftentimes subtle) havoc until I fix all of the callers. Thanks for all the support, and have a great weekend! Steve
smime.p7s
Description: S/MIME Cryptographic Signature
