Unfortunately in this case it doesn't seem to be very feasable. The problem is that almost all of the calls within the module are hard wired to each other. Even though there is a Benchmark object (blessed using the single argument form!) none of the routines take $self references so they can't be called as methods, and should I call one as a procedure then it will call all of its friends as procedures, completely ignoring what overriden methods I have provided.

So the question for me was total ground up rewrite in my own module or to convert the entire thing into an OO version?

I chose the later and have now completed the majority of work converting it into an OO structure. This basically meant trawling the code for subroutines and subroutine calls and adding in a $self pointer, splitting out functionality into different objects etc. Now I could reimplement the original package just through calls to mine, but no way I could go the other way.

Once Im done I plan to post it here for revue and comments.

Although as the module has no copyright information I think I might need permission.

Yves
--
You are not ready to use symrefs unless you already know why they are bad. -- tadmc (CLPM)