note sundialsvc4 <p> For my (possibly unrelated ...?) purposes, it would need to be being able to build a more isolated test case situation, especially for adding instrumentation to an existing, complex but poorly-designed class structure ... without significantly changing the crufty old code, if at all. </p><p> I have noticed that heavily class-based code <em>over time</em> can wind up having a lot of &ldquo;side effects,&rdquo; for lack of a more proper term, which can make it difficult to deduce exactly which code-path is being taken. &nbsp; And, when you don&rsquo;t yet really know whether any particular one of those paths are or are not reliable, that&rsquo;s a big deal, at least in my situation. &nbsp; (I mostly deal with legacy code ... eight years old or more ... stuff that stinks but drives businesses.) &nbsp; I don&rsquo;t want to &ldquo;hijack&rdquo; this particular thread into that direction, though, but I&rsquo;m interested. </p> 996022 996190