Check the code, it's not using 'supports recursion' anymore. On Wed, Jan 14, 2009 at 3:31 AM, Maciej Paszta <[email protected]> wrote: > Krzysztof Koźmic wrote: >> >> These changes were made as a result of moving Castle Stack to .net 3.5. >> If you need to maintain Mono compatibility, I'd suggest use last release >> .net-2.0-compatibile (it's a tag in the repository). >> How important is it for you to run on the trunk? >> Are you using any recently (within last month) added features? > > Is LockRecursionPolicy really necessary here? I'm aware that > ReaderWriterLockSlim is better than it's predecessor but according to msdn > LockRecursionPolicy.SupportsReccursion is not recommended for a new code > ("it introduces unnecessary complications and makes your code more prone to > deadlocks"). So maybe it's better to use standard policy (no recursion) and > introduce safer code, instead of hanging to old behavior (SupportsRecursion > makes ReaderWrtierLockSlim work like a ReaderWriterLock)? > > > Link to MSDN: > http://msdn.microsoft.com/en-us/library/system.threading.readerwriterlockslim.aspx > <http://msdn.microsoft.com/en-us/library/system.threading.lockrecursionpolicy.supportsrecursion.aspx> > >
-- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
