Introducing a Memory-Safe Successor Language in Large C++ Code Bases

Introducing a Memory-Safe Successor Language in Large C++ Code Bases

CppNow via YouTube Direct link

The Second System Effect

27 of 31

27 of 31

The Second System Effect

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Introducing a Memory-Safe Successor Language in Large C++ Code Bases

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Introduction
  2. 2 Apples predecessor languages
  3. 3 Problems with C
  4. 4 Mitigation
  5. 5 The biggest problem
  6. 6 Uninitialized memory
  7. 7 Initialize local variables
  8. 8 The real problem
  9. 9 Integer overflow
  10. 10 Bounce checks
  11. 11 pointers and local reasoning
  12. 12 pointers follow stricter rules
  13. 13 Can we fix these problems without a new language
  14. 14 Our successful language is Swift
  15. 15 Swift is a successful language
  16. 16 Local variables
  17. 17 Types
  18. 18 Undefined Behavior
  19. 19 Generic Functions
  20. 20 Swift
  21. 21 Swift Exceptions
  22. 22 Concurrency
  23. 23 Data Isolation
  24. 24 Moving This Way
  25. 25 Three Key Ideas
  26. 26 Be Incremental
  27. 27 The Second System Effect
  28. 28 You Never Succeed
  29. 29 Refactor
  30. 30 Moving Forward
  31. 31 Team Psychology

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.