[Mono-devel-list] Question Threads and Locks

[Paolo Molaro]

On 01/19/05 Christoph Stiedl wrote:
> The problem is that some reads aren't locked and some are, maybe because the
> values don't change,... - but thats the problem, I didn't find any
> documentation about it and so I started by reading the source code. As
> anybody can imagine it's difficult to figure out, which values can change,
> which not, which variables need to be locked when read,... - thats only
> possible if you know all of the code, or if you wrote the code yourself. And
> thats the reason why I asked for help, because I don't know all of the code.

This stuff needs to be documented and the way to do it is to
read the code, use grep and annotate it. Anyone can do it.
Would you like to contribute?
If you don't plan to contribute in the effort and just need a quick
help on a data structure in particular, just ask explicitly
what you need. Asking a list of all the shared data is not going to
get an answer, because this stuff isn't documented yet and doing so
_now_ is not scheduled for any of us: it takes time. You can help by taking
a data structure and documenting that for starters, if you want.
Plus, having more eyes on the code can only help find and fix the bugs
that lurk in there. Right now, if I had a document describing what is
shared and which locks protect what, I wouldn't tell you, because
that would prevent you from reading the code and telling us about the
bugs you found;-)

lupus

-- 
-----------------------------------------------------------------
lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better