Bob Rogers wrote: > I think I'm already well past that point in terms of option-parsing > complexity. I have places where the command_line_options method calls > SUPER::command_line_options in order to replace/rename options, so I > need some way to supercede and/or rename things.
got it. I had to double check Getopt::Declare's documentation. It doesn't appear to do anything that would allow you to replace/rename options once the object is created. Or, at least, it doesn't have anything documented to explain that. You could conceivably do it by parsing the big string before you pass it to Getopt::Declare. You could create a simple grammar in Parse::RecDescent to parse the string, and then make a "rule search/replace/rename" function. I'm not sure how the Getopt::Declare object is structured. I don't know if you could concievably have hooks into each individual options name/handler. That would be the ideal situation, but I'm not familiar enough with it to know if the information is there and it's undocumented, or if its an amorphous block. A quick email to Damian with your rule search/replace/rename question might get you a quick answer. who knows, Damian might be able to tweak it while he's on a long flight somewhere. If you figure something out, lemme know. I could probably use it too. _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
