| PrintNumber | ErrorLocation | Error | Correction | DateAdded |
|---|---|---|---|---|
| 4 | piv | Fourth Printing, December 2010, |
Fourth Printing, December 2010, corrections made March 2011 |
6/5/2008 |
| 4 | pvii | 1.1.5 Robustness | 1.1.5 Reliability | 3/21/2011 |
| 4 | pxvii | You must have a working knowledge of fundamental LabVIEW principles and terminology, as instructed in a LabVIEW Basics I and II hands-on course3, and experience developing and deploying applications. | You must have a working knowledge of fundamental LabVIEW principles and terminology, as instructed in a LabVIEW Core I and II hands-on course3, and experience developing and deploying applications. | 3/21/2011 |
| 4 | pxix | 2. Bloomy Controls is a National Instruments Select Integration Partner with offices in Windsor, Connecticut; Milford, Massachusetts; and Fort Lee, New Jersey. Information is available at www.bloomy.com. 3. LabVIEW Basics I and II is a one-week hands-on course offered by NI Certified Training Centers. More information is available from http://www.ni.com/training. |
2. Bloomy Controls is a National Instruments Select Integration Partner with offices in Windsor, Connecticut; Marlborough, Massachusetts; and Fort Lee, New Jersey. Information is available at www.bloomy.com. 3. LabVIEW Core I and II is a one-week hands-on course offered by NI Certified Training Centers. More information is available from http://www.ni.com/training. |
3/21/2011 |
| 4 | p2 | Some styles lend themselves to better performance, source code that is easier to read and maintain, and applications that are more reliable and robust. Hence, I present Theorem 1.1: Theorem 1.1: A direct relationship exists between LabVIEW development style and the ease of use, efficiency, readability, maintainability, robustness, simplicity, and performance of the completed application. |
Some styles lend themselves to better performance, source code that is easier to read and maintain, and applications that are more reliable. Hence, I present Theorem 1.1: Theorem 1.1: A direct relationship exists between LabVIEW development style and the ease of use, efficiency, readability, maintainability, reliability, simplicity, and performance of the completed application. |
3/21/2011 |
| 4 | p6 | Let us break down Theorem 1.1 into seven different parts and evaluate each one individually: ease of use, efficiency, readability, maintainability, robustness, simplicity, and performance. | Let us break down Theorem 1.1 into seven different parts and evaluate each one individually: ease of use, efficiency, readability, maintainability, reliability, simplicity, and performance. | 3/21/2011 |
| 4 | p12 | 1.1.5 Robustness A LabVIEW application is robust if it is bug free and never crashes. LabVIEW provides fundamental constructs that promote robust applications, including subVIs and error handling, as well as fundamental elements such as local and global variables that can hinder applications when used improperly. |
1.1.5 Reliability A LabVIEW application is reliable if it is bug free and never crashes. LabVIEW provides fundamental constructs that promote reliable applications, including subVIs and error handling, as well as fundamental elements such as local and global variables that can hinder applications when used improperly. |
3/21/2011 |
| 4 | p13 | Error handling is critical for robust application performance. | Error handling is critical for reliable application performance. | 3/21/2011 |
| 4 | p14 | Overall, Meticulous VI is the most robust in terms of error handling. Proper error handling is an essential ingredient for reliable and robust applications. | Overall, Meticulous VI is the most reliable in terms of error handling. Proper error handling is an essential ingredient for reliable applications. | 3/22/2011 |
| 4 | p14 | Hence, Nested VI is the most robust in terms of fewest write variables. Chapter 4 discusses variables in greater detail. The rules presented throughout this book ensure robust applications. | Hence, Nested VI is the most reliable in terms of fewest write variables. Chapter 4 discusses variables in greater detail. The rules presented throughout this book ensure reliable applications. | 3/22/2011 |
| 4 | p17 | Robustness (see Section 1.1.5) also is required. If the application is not reliable and robust, performance is meaningless. | Reliability (see Section 1.1.5) also is required. If the application is not reliable, performance is meaningless. | 3/22/2011 |
| 4 | p18 | The VI Metrics window determines simplicity (see Section 1.1.6) and is used to calculate the modularity index to help evaluate robustness (see Section 1.1.5). | The VI Metrics window determines simplicity (see Section 1.1.6) and is used to calculate the modularity index to help evaluate reliability (see Section 1.1.5). | 3/22/2011 |
| 4 | p46 | 4. Bloomy Controls is an NI Select Integration Partner that provides systems development and training services throughout the Northeast United States, including offices in Windsor, Connecticut; Milford, Massachusetts; and Fort Lee, New Jersey. |
4. Bloomy Controls is an NI Select Alliance Partner that provides systems development and training services throughout the Northeast United States, including offices in Windsor, Connecticut; Marlborough, Massachusetts; and Fort Lee, New Jersey. |
3/23/2011 |
| 4 | p62 | Create intuitive GUI VIs that are robust and self-explanatory, and do not require textual explanations. | Create intuitive GUI VIs that are reliable and self-explanatory, and do not require textual explanations. | 3/23/2011 |
| 4 | p71 | Color versions of those example panels can be freely downloaded from the Publisher’s website page for this book at www.prenhallprofessional.com/title/0131458353. An electronic (eBook) version of this book containing full-color illustrations is available for purchase from www.prenhallprofessional. com/title/0132414813. |
Color versions of those example panels can be freely downloaded from the Publisher’s website page for this book at www.informit.com/title/9780131458352. An electronic (eBook) version of this book containing full-color illustrations is available for purchase from www.informit.com/title/9780132414814. |
3/23/2011 |
| 4 | p154 | This pattern provides nine terminals within the icon’s border, five of which are assigned. Figure 5-24 updated. |
This pattern provides nine terminals within the icon’s border, four of which are assigned. fixed |
3/23/2011 |
| 4 | p155 | 1. Color versions of the example illustrations in Chapter 5 can be freely downloaded from the Publisher’s website page for this book at www.prenhallprofessional.com/title/0131458353. For full-color illustrations, the electronic (eBook) version of The LabVIEW Style Book is available for purchase from www.prenhallprofessional.com/title/0132414813. | 1. Color versions of the example illustrations in Chapter 5 can be freely downloaded from the Publisher’s website page for this book at www.informit.com/title/9780131458352. For full-color illustrations, the electronic (eBook) version of The LabVIEW Style Book is available for purchase from www.informit.com/title/9780132414814. | 3/23/2011 |
| 4 | p180 | ...options we provide the user, the less robust our software is. As per Theorem 3.1, reliability is the developer’s responsibility. | ...options we provide the user, the less reliable our software is. As per Theorem 3.1, reliability is the developer’s responsibility. | 3/23/2011 |
| 4 | p212 | Figure 7-9A error | replaced | 3/23/2011 |
| 4 | p225 | ...nodes help the developer understand how they work and help ensure reliable and robust applications. | ...nodes help the developer understand how they work and help ensure reliable applications. | 3/23/2011 |
| 4 | p228 | Its purpose is to programmatically reset the error cluster with no error. Depending on the value of Clear Mode, it resets the error code always or just when the error code equals the programmed Code to Clear. | Its purpose is to programmatically reset the error cluster with no error when the error in cluster’s error code contains the programmed value of Code to Clear. Alternatively, the VI resets all errors or warnings if the Code to Clear terminal is unwired or 0. | 3/23/2011 |
| 4 | p229 | Figure 7-16 Clear Error All or Specified VI is a utility that selectively clears errors according to the values of Clear Mode and Code to Clear. Figure replaced. |
Figure 7-16 Clear Error All or Specified VI is a utility that selectively clears errors and warnings according to the value of Code to Clear. fixed |
3/23/2011 |
| 4 | p239 | As discussed in Chapter 1, “The Significance of Style,” good style means good readability, maintainability, reliability, efficiency, robustness, simplicity, and performance. | As discussed in Chapter 1, “The Significance of Style,” good style means good readability, maintainability, reliability, efficiency, simplicity, and performance. | 3/23/2011 |
| 4 | p252 | Figure 8-6B replaced and Value Change in caption should be bold. | fixed | 3/23/2011 |
| 4 | p253 | Figure 8-6C replaced | fixed | 3/23/2011 |
| 4 | p260-261 | Figure 8-12 and 8-13 replaced | fixed | 3/23/2011 |
| 4 | p264 | Figure 8-14C replaced | fixed | 3/23/2011 |
| 4 | p319 | Most importantly, code reviews help ensure high quality software that is readable, maintainable, and robust. | Most importantly, code reviews help ensure high quality software that is readable, maintainable, and reliable. | 3/23/2011 |
| 4 | p323 | As discussed in Chapter 7, “Error Handling,” error trapping is an essential ingredient of error handling, and error handling facilitates robust applications. | As discussed in Chapter 7, “Error Handling,” error trapping is an essential ingredient of error handling, and error handling facilitates reliable applications. | 3/24/2011 |
| 4 | p336 | Moreover, code reviews enforce the style conventions, which improve the ease of use, efficiency, readability, simplicity, performance, maintainability, and robustness of your LabVIEW applications. | Moreover, code reviews enforce the style conventions, which improve the ease of use, efficiency, readability, simplicity, performance, maintainability, and reliability of your LabVIEW applications. | 3/24/2011 |
| 4 | p338 | 1. A custom test configuration file and a style checklist document in electronic form can be downloaded from www.bloomy.com/lvstyle. “Advice for VI-Based Code Reviews,” NIWeek2006 presentation by Doug Norman of National Instruments. |
1. A custom test configuration file and a style checklist document in electronic form can be downloaded from www.bloomy.com/lvstyle. 2. “Advice for VI-Based Code Reviews,” NIWeek2006 presentation by Doug Norman of National Instruments. |
3/24/2011 |
| 4 | p340 | code review Systematic method of reviewing source code quality for readability, maintainability, and robustness, utilizing one or more independent perspectives or reference points. | code review Systematic method of reviewing source code quality for readability, maintainability, and reliability, utilizing one or more independent perspectives or reference points. | 3/24/2011 |
| 4 | p347 | robust Characteristic of a LabVIEW application if it performs reliable error handling and shuts down gracefully. |
reliable Characteristic of a LabVIEW application if it performs reliable error handling and shuts down gracefully. |
3/24/2011 |
| 4 | p349-355 | High priority rules should be in bold. |
fixed | 3/24/2011 |
| 4 | p360, 365, 370 | robustness, 12-15 | reliability, 12-15 | 3/24/2011 |
| 4 | p377 | www.prenhallprofessional.com/safarienabled | www.informit.com/safarienabled | 3/24/2011 |