Indeed. I've actually made suggestions for a few new rules that should bubble up quite a few bugs in the framework (assuming they haven't already been found and fixed for 3.0...).
On Fri, 11 Aug 2006 16:05:54 -0400, =?ISO-8859-1?Q?S=E9bastien_Lorion?= <[EMAIL PROTECTED]> wrote: >Good news! I hope they will also remove this kind of code from .NET ... > >Using CodeSearch addin for Reflector, we can easily see that many >holes are left open. > >http://www.gotdotnet.com/workspaces/workspace.aspx?id=884b469a-4b88-4b20- 8747-b3ff6bb13a49 > >Sébastien > >On 8/11/06, Peter Ritchie ><[EMAIL PROTECTED]> wrote: >> Just heard word that the Orcas release of Visual Studio Code Analysis (and >> FxCop, I'm assuming) will contain a check for lock(this) and SyncLock Me. >> So, documentation and sample code should have lock(this) removed around >> the RTM for Orcas, I hope. So, people should learn pretty quickly after >> that... >> >> On Fri, 11 Aug 2006 11:43:56 -0400, =?ISO-8859-1?Q?S=E9bastien_Lorion?= >> <[EMAIL PROTECTED]> wrote: >> >> >Even the lock code snippet in VS 2005 suggests "this" as a default >> >value. How do they expect people to learn ? >> > >> >Btw, locking on a string is not a good idea either because since >> >strings are immutable, they can be shared/interned, thus they may be >> >publicly accessible too. >> > >> >Sébastien >> >> =================================== >> This list is hosted by DevelopMentor(r) http://www.develop.com >> >> View archives and manage your subscription(s) at http://discuss.develop.com >> > > >-- >Sébastien Lorion >Software Architect / Architecte organique >[EMAIL PROTECTED] > >=================================== >This list is hosted by DevelopMentor® http://www.develop.com > >View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
