On 4/25/2012 1:12, Invisible wrote:
> You do all of that stuff from /outside/ your transactions, that's all.

Except that .NET is about components, so that doesn't work out too well.

And if you're talking about putting Haskell on .NET, then your entire 
program becomes one "transaction". (Note we've moved to talking about STM 
from talking about Haskell, which was not my intention. It was an analogy.)

> Remember, transactions are only for thread communication. You start a
> transaction, fetch the next work item from the shared work queue, and the
> transaction. Then you process the work item, calling whatever libraries you
> need. Simples.

And if the work item is in a class written that does I/O to obtain it, or to 
log a message, or etc etc etc?

-- 
Darren New, San Diego CA, USA (PST)
   "Oh no! We're out of code juice!"
   "Don't panic. There's beans and filters
    in the cabinet."

Post a reply to this message