issue added http://support.castleproject.org/projects/IOC/issues/view/IOC-ISSUE-173
BTW I am trying to keep these patches to a managable and understandable size so as to not make them too much of an issue to apply. Let me know if I should be doing more or less in each patch. On Dec 16, 12:55 am, Krzysztof Koźmic (2) <[email protected]> wrote: > sure, go ahead, I'm sure your is more polished than mine. > > On 15 Gru, 14:44, Krzysztof Koźmic (2) <[email protected]> wrote: > > > See this. You'll need to change the extension to .patch > > > This is my rather quick attempt at removing non-generic collections > > from the > > codebase.http://wiki.kozmic.pl/GetFile.aspx?File=%2fnon-generic-collections-re... > > > On 15 Gru, 14:34, Simon <[email protected]> wrote: > > > > and how about in \InversionOfControl\src\Castle.MicroKernel\Lifestyle > > > \Pool\DefaultPool.cs > > > > it would seem syncronization is redundant here because all usages of > > > "inUse" are wrapped in a ReaderWriterLock > > > > On Dec 16, 12:15 am, Krzysztof Ko 1/4 mic (2) <[email protected]> wrote: > > > > > yes, as far as I can tell it is redundant. > > > > > On 15 Gru, 14:07, Simon <[email protected]> wrote: > > > > > > In the file > > > > > \InversionOfControl\src\Castle.MicroKernel\SubSystems\Naming > > > > > \KeySearchNamingSubSystem.cs > > > > > > It makes use of Hashtable.Synchronized and ArrayList.Synchronized. > > > > > > But since all the methods on KeySearchNamingSubSystem have the > > > > > attribute [MethodImpl(MethodImplOptions.Synchronized)] doesnt that > > > > > make syncronizing the collections redundant? -- 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.
