TAILIEUCHUNG - Chapter 11 Separate Compilation and Namespaces

All code goes in some namespace Unless specified global namespace, No need for using directive. Global namespace always available, Implied "automatic" using directive | Chapter 11 Separate Compilation and Namespaces Learning Objectives Separate Compilation Encapsulation reviewed Header and implementation files Namespaces using directives Qualifying names Unnamed namespaces Hiding helping functions Nested namespaces Separate Compilation Program Parts Kept in separate files Compiled separately Linked together before program runs Class definitions Separate from "using" programs Build library of classes Re-used by many different programs Just like predefined libraries Class Separation Class Independence Separate class definition/specification Called "interface" Separate class implementation Place in two files If implementation changes only that file need be changed Class specification need not change "User" programs need not change Encapsulation Reviewed Encapsulation principle: Separate how class is used by programmer from details of class’s implementation "Complete" separation Change to implementation NO impact on any other programs Basic OOP .

• Kỹ thuật lập trình
• Separate Compilation
• Encapsulation Reviewed
• Encapsulation Rules
• More Class Separation
• Class Header Files
• Other Library Files
• Global Namespace
• Lecture CIS 190
• C++ programming
• Lecture C++ programming
• Compiling multiple
• Linking multiple