81 ;;Quote: class-based APIs are easier to modify than interface-based APIs; can add members to classes as needed

81 ;;Quote: use abstract classes to decouple contract from implementation; use interfaces to define invariant contracts

120 ;;Quote: use properties for simple access to simple data with a simple computation

138 ;;Quote: every event has two arguments, a sender object and eventArgs; provides scope to the sender and arguments of the event as a versioned class

169 ;;Quote: be careful of making members virtual; they cause subtle and complex observable behaviors and subclass interactions

172 ;;Quote: provide reference tests for abstractions; confirm that users implement the contract

179 ;;Quote: exceptions promote API consistency; designed for failure reporting and nothing else; while return values have many uses, e.g., Win32 API

179 ;;Quote: object-oriented frameworks can not standardize on return-value-based error reporting

180 ;;Quote: if using return values, error handling code must be near the code that could fail

180 ;;Quote: error codes are often ignored; exceptions are impossible to ignore, improving robustness

182 ;;Quote: exceptions carry rich information describing the cause of the failure

183 ;;Quote: exceptions promote instrumentation; for example, debuggers can break when an exception is thrown

204 ;;Quote: the try-parse pattern reports failure instead of an exception; avoids performance problem for a common scenario

242 ;;Quote: allow default constructor plus property setters in place of a parameterized constructor

275 ;;Quote: avoid unnecessary spaces

278 ;;Quote: order class members by field, constructors, properties, methods, events, implementation, private members, and nested types