Overview • The process of building a program • What a translation unit (TU) is, and its relationship to the code you write • The phases of translation • Declarations, definitions, and linkage • The one-definition compilation process translation • In C++, translation is performed upon a translation unit (TU) in nine well- defined stages • Evocatively named Phases 1 through 9 • A translation unit is defined (roughly) The Structure of a Program 20Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Phases of Translation 21 CppCon 2020 - The Structure of a Program Phase 1 Phase 2 Phase 3 Phase 4 Phase 5 Phase

lambda functionsCppCon 2021 – Back to Basics: Templates – Part 1 Copyright © 2021 Bob Steagall Translation Units • Compilation • The process of converting human-readable source code into binary object standard calls the compilation process translation 25CppCon 2021 – Back to Basics: Templates – Part 1 Copyright © 2021 Bob Steagall Translation Units • In C++, translation is performed in nine well-defined These are what we usually refer to as pre-processing • The output of Phase 6 is a translation unit • A translation unit is defined [5.1] as • A source file • Plus all the headers and source files included

In this talk I'll tell you about C++ AoT compiler, JiTs for dynamic language, JiTs for binary translation, and dive back 20, 30, 40, 50, 60 years, way back into compiler history and read wonderful academic “just-in-time” compilation (JiT) techniques since the 1960s. Broadly, JiT compilation includes any translation performed dynamically, after a program has started execution. We examine the motivation behind “just-in-time” compilation (JiT) techniques since the 1960s. Broadly, JiT compilation includes any translation performed dynamically, after a program has started execution. We examine the motivation behind

utils.module_loading django.utils.safestring django.utils.text django.utils.timezone django.utils.translation Validators Writing validators How validators are run Built-in validators Built-in Views Serving login screen: Since translation is turned on by default, the login screen may be displayed in your own language, depending on your browser’s settings and if Django has a translation for this language. wanted to customize the wording of all user facing strings for the name field: from django.utils.translation import gettext_lazy as _ class AuthorForm(ModelForm): class Meta: model = Author

utils.module_loading django.utils.safestring django.utils.text django.utils.timezone django.utils.translation Validators Writing validators How validators are run Built-in validators Built-in Views Serving local domain – e.g., http://127.0.0.1:8000/admin/. You should see the admin’s login screen: Since translation is turned on by default, if you set LANGUAGE_CODE, the login screen will be displayed in the given wanted to customize the wording of all user facing strings for the name field: from django.utils.translation import gettext_lazy as _ class AuthorForm(ModelForm): class Meta: model = Author

utils.module_loading django.utils.safestring django.utils.text django.utils.timezone django.utils.translation django.utils.tzinfo Validators Writing validators How validators are run Built-in validators screen: Since translation is turned on by default, the login screen may be displayed in your own language, depending on your browser’s settings and on whether Django has a translation for this language format_html_join, smart_urlquote from django.utils.text import Truncator from django.utils.translation import ugettext as _ from django.utils.safestring import mark_safe @@ -306,6 +306,18 @@ class

dev20180306181007 Since translation is turned on by default, the login screen may be displayed in your own language, depending on your browser’s settings and on whether Django has a translation for this language format_html, format_html_join, smart_urlquote from django.utils.text import Truncator from django.utils.translation import ugettext as _ from django.utils.safestring import mark_safe @@ -306,6 +306,18 @@ class wanted to customize the wording of all user facing strings for the name field: from django.utils.translation import ugettext_lazy as _ class AuthorForm(ModelForm): class Meta: model = Author fields = ('name'

utils.module_loading django.utils.safestring django.utils.text django.utils.timezone django.utils.translation Validators Writing validators How validators are run Built-in validators Built-in Views Serving login screen: Since translation is turned on by default, the login screen may be displayed in your own language, depending on your browser’s settings and if Django has a translation for this language. wanted to customize the wording of all user facing strings for the name field: from django.utils.translation import ugettext_lazy as _ class AuthorForm(ModelForm): class Meta: model = Author

utils.module_loading django.utils.safestring django.utils.text django.utils.timezone django.utils.translation Validators Writing validators How validators are run Built-in validators Built-in Views Serving login screen: Since translation is turned on by default, the login screen may be displayed in your own language, depending on your browser’s settings and if Django has a translation for this language. wanted to customize the wording of all user facing strings for the name field: from django.utils.translation import ugettext_lazy as _ class AuthorForm(ModelForm): class Meta: model = Author

dev20200305075726 Since translation is turned on by default, the login screen may be displayed in your own language, depending on your browser’s settings and if Django has a translation for this language. wanted to customize the wording of all user facing strings for the name field: from django.utils.translation import ugettext_lazy as _ class AuthorForm(ModelForm): class Meta: model = Author fields = ('name' enabled, the active language may be set using translation.override(): from django.utils import translation def test_language_using_override(self): with translation.override('fr'): response = self.client.get('/')