in reply to Re: Module development: concurrent versions (Updated)
in thread Module development: concurrent versions (Updated)

Yeah. I've done that before, but it means that you cannot use the two versions in the same program.

The problem I'm trying to track down only manifests itself when the size of the arrays being sized gets above about 500,000 elements which make comparing trace output by eye impossible. So then you want to automate the comparison--diff or a custom script--but doing this with trace lines that (have to) contain addresses, means that all lines are different. (Ie. as different modules are loaded, the memory allocator has been exercised in different ways, so the addresses of test arrays and its elements are all different.)

I needed to be able to load both modules concurrently so I can run them on the same array. I now can, but getting there was messy.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
  • Comment on Re^2: Module development: concurrent versions (Updated)