On Designing Good Libraries

Brad Abrams On Designing Good Libraries | Paid Surveys

Brad Abrams On Designing Good Libraries | Paid Surveys — Sat, 30 May 2009 04:02:32 GMT

PingBack from http://paidsurveyshub.info/story.php?title=brad-abrams-on-designing-good-libraries

FxCop and Guidelines

Dan McKinley — Tue, 28 Dec 2004 00:54:00 GMT

Designing .NET Class Libraries videos coming soon

Brad Abrams — Mon, 27 Dec 2004 23:05:00 GMT

re: Finally

.NET Forever — Fri, 05 Nov 2004 17:38:00 GMT

Do return an empty array instead of a null reference

Web Log di Adrian Florea — Fri, 27 Aug 2004 21:50:00 GMT

Qualche linea guida di design di librerie

Tutto fa .NET — Fri, 27 Aug 2004 19:45:00 GMT

Good practice

C#deSamurai — Thu, 26 Aug 2004 19:35:00 GMT

Software development -- Engineering or Art

Brad Abrams — Wed, 14 Apr 2004 06:28:00 GMT

Software development -- Engineering or Art

Brad Abrams — Wed, 14 Apr 2004 01:18:00 GMT

RE: On Designing Good Libraries

Frank Hileman — Fri, 11 Jul 2003 04:12:00 GMT

Cloning the returned collection in a property get is HORRIBLE, HORRIBLE, HORRIBLE!! I realize it is a security issue. But it is also a scalibility issue. If the collection can get arbitrarily large, or it is accessed within loops, it can bring an application to its knees! The real problem is a lack of a simple way to create read-only collections. Currently the only way is to create another class, that wraps your collection class, but is read only. There should be a simpler way built into the languages or the CLR. Then these large collections would not have to be cloned and garbage collected.