Abstract
Many object-oriented languages—C# included—don’t offer anything to force developers to create well-designed software. There is no better example of this than when using C++ to implement an OO design. C# is a little more structured than C++; for example, you cannot create free static functions that exist outside the context of a defined type. Still, C# doesn’t force you to create software that adheres to well-known practices of good software design.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Full coverage of custom attributes in the.NET Framework is beyond the scope of this book. For more information, consult the MSDN Library documentation or any one of the fine books covering the CLR, such as Andrew Troelsen’s Pro C# with.NET 3.0 (Berkeley, CA: Apress, 2007).
For those of you curious about the curious name of this field, read about the Pimpl Idiom in Herb Sutter’s Exceptional C++: 47 Engineering Puzzles, Programming Problems, and Exception-Safety Solutions (Boston: Addison-Wesley Professional, 1999).
Rights and permissions
Copyright information
© 2010 Trey Nash
About this chapter
Cite this chapter
Nash, T. (2010). In Search of C# Canonical Forms. In: Accelerated C# 2010. Apress. https://doi.org/10.1007/978-1-4302-2538-6_13
Download citation
DOI: https://doi.org/10.1007/978-1-4302-2538-6_13
Publisher Name: Apress
Print ISBN: 978-1-4302-2537-9
Online ISBN: 978-1-4302-2538-6
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)