Implementation of a "Transaction" entity for storing logs in data objects

[iustin94]

Has it been considered the option of expanding the library so that instead of using directly the logger to a TextWriter, a transaction history could instead be stored in the simulation, which then can be in return used for outputting to the textwriter, or passing the transaction objects to a different client who can then parse it directly, rather than having to process the logger text?

[abeham]

I haven't considered such options. Do you have an examplary design? Also, can't you do that in your simulation code, i.e. when your process is active it logs to an object that you know of. What would be the benefit of having it inside the Sim# library?

[iustin94]

That was my plan :) the benefit would be of including it inside of the library, if it was a case common to use.