Abstract
Many object-oriented languages—VB included—do not offer anything to force developers to create well-designed software. In much the same way that design patterns evolved, the development community has identified best practices useful for designing types to meet a specific purpose. We will present these practices as a set of checklists, or recipes, that you can use while designing new classes. Before a pilot can clear an airplane to back out of the gate, he must go through a strict checklist. The goal of this chapter is to identify such checklists for creating robust types in the VB world.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Literatur
To find out more about the curious name of the pimp1 field, read about the Pimpl Idiom in Herb Sutter’s Exceptional C++: 47 Engineering Puzzles, Programming Problems, and Solutions (Addison-Wesley Professional, 1999).
Rights and permissions
Copyright information
© 2008 Guy Fouché and Trey Nash
About this chapter
Cite this chapter
(2008). VB 2008 Best Practices. In: Accelerated VB 2008. Apress. https://doi.org/10.1007/978-1-4302-0339-1_14
Download citation
DOI: https://doi.org/10.1007/978-1-4302-0339-1_14
Publisher Name: Apress
Print ISBN: 978-1-59059-874-0
Online ISBN: 978-1-4302-0339-1
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)