From: SourceForge.net <no...@so...> - 2007-04-03 16:48:05
|
Bugs item #1693765, was opened at 2007-04-03 18:48 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=416078&aid=1693765&group_id=36057 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: MSDN Documenter Group: v1.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Robert Wenner (robertwenner) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong threadsafety summary Initial Comment: NDoc always generates that silly thread-safety section that the MSDN libray also has: Public static (Shared in Visual Basic) members of this type are safe for multithreaded operations. Instance members are not guaranteed to be thread-safe. This is nonsense since there is no guarantee that a static method will not access global variables, singletons, files, network connections and so on without proper synchronization. Please do not generate this by default. At least add a switch to disable this. Adding a <threadsafety> tag to all my classes is just cumbersome. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=416078&aid=1693765&group_id=36057 |