in reply to Re: Testing -- making a new constructor behave differently for one package
in thread Testing -- making a new constructor behave differently for one package

Actually the name of the class I'm using is not hardcoded, and I believe the accessor where I get the name of the package to use might be an easier point to hijack the object creation instead of the actual new method. Thanks Chromatic!
  • Comment on Re^2: Testing -- making a new constructor behave differently for one package