Hello, In .NET Framework GC can only collect objects that have zero reference count (or WeakReference'd types). AFAIK releasing in windsor nulls inner references held in windsor container to the resolved object, this enables GC to collect unused object's memory space. But again a GC Collect call must be invoked by someone sometime (usually by CLR).
So in C# and with Windsor, releasing only opens way to real memory collection done by garbage collector, but in (unmanaged) C++ you delete manually doing real memory management. Cheers, Berke Sökhan. 2011/5/26 mynkow <[email protected]> > true... > > but if I have to release those objects manually why we should have GC? > > PS: I know that the functions of GC are more complicated and how it > works.... > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" 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-users?hl=en. > -- Berke SOKHAN. http://twitter.com/berkesokhan http://blog.berkesokhan.com http://www.birliktegelistir.com/editors.aspx -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en.
