 |
|
|
|
|
1.5.2. Legibility |
|
|
|
| |
|
|
|
|
|
1.5.3. Portability |
|
|
|
| |
|
|
|
|
|
1.5.4. Speed and Efficiency |
|
|
|
| |
|
|
|
|
|
1.6. Coding Style and Conventions |
|
|
|
| |
|
|
|
|
|
1.6.1. Function Name Conventions |
|
|
|
| |
|
|
|
|
|
1.6.2. Header File Conventions |
|
|
|
| |
|
|
|
|
|
1.6.3. Legibility Considerations |
|
|
|
| |
|
|
|
|
|
1.6.4. Consistency and Automation Considerations |
|
|
|
| |
|
|
|
|
|
1.7. Standards Followed in This Book |
|
|
|
| |
|
|
|
|
|
1.8. Y2K or "Buddy, Can You Spare $600,000,000,000?" |
|
|
|
| |
|
|
|
|
|
1.8.1. Characterizing Y2K |
|
|
|
| |
|
|
|
|
|
1.8.2. A.D. 2000 in the Western Calendar |
|
|
|
| |
|
|
|
|
|
1.8.3. Strategies and Techniques for Y2K Fixes |
|
|
|
| |
|
|
|
|
|
1.8.4. Other Flavors of Doomsday |
|
|
|
| |
|
|
|
|
|
1.8.5. Resources |
|
|
|
| |
| |
|
|
|
|
|
2.1. Introduction |
|
|
|
| |
|
|
|
|
|
2.1.1. Time A Definition |
|
|
|
| |
|
|
|
|
|
2.1.2. Calendars As the Historical Basis of Timekeeping |
|
|
|
| |
|
|
|
|
|
2.1.3. Applied Astronomy |
|
|
|
| |
|
|
|
|
|
2.2. Astronomical Units |
|
|
|
| |
|
|
|
|
|
2.2.1. The Day |
|
|
|
| |
|
|
|
|
|
2.2.2. The Year |
|
|
|
| |
|
|
|
|
|
2.2.3. The Month |
|
|
|
| |
|
|
|
|
|
2.3. The Week |
|
|
|
| |
|
|
|
|
|
2.4. What You Need Date/Time Code to Do |
|
|
|
| |
|
|
|
|
|
2.5. A Linear Time Scale |
|
|
|
| |
|
|
|
|
|
2.5.1. Why You Need One |
|
|
|
| |
|
|
|
|
|
2.5.2. The Julian Day Number |
|
|
|
| |
|
|
|
|
|
2.6. Calendric Terminology and Definitions |
|
|
|
| |