Tux Machines

Programming Leftovers

Posted by Roy Schestowitz on Mar 09, 2023

today's leftovers

Events: Debconf, FOSDEM, and SCaLE

Formalizing Stability and Resilience Properties

↺ Formalizing Stability and Resilience Properties

> Sent to me via mailbag:

↺ mailbag

↺ mailbag

Book review - Practical Design Patterns for Java Developers

↺ Book review - Practical Design Patterns for Java Developers

> The goal of the book wants to break a returning pattern many programmers go through during their careers. When you start using a programming language like Python, JavaScript, or even Java, the platform allows you to create messy code. It’s only when you learn and understand patterns and debugging, and use a strongly typed language like Java, that you start writing “real” code. When someone starts a programming career with Java and has a solid understanding of design patterns, a lot of bad practices can be avoided.

Jan Grulich: Explained: QGnomePlatform and Adwaita-qt

↺ Jan Grulich: Explained: QGnomePlatform and Adwaita-qt

Compiler optimization and its effect on debugger line information

↺ Compiler optimization and its effect on debugger line information

> In my previous article, I described the DWARF information used to map regular and inlined functions between an executable binary and its source code. Functions can be dozens of lines, so you might like to know specifically where the processor is in your source code. The compiler includes information mapping between instructions and specific lines in the source code to provide a precise location. In this article, I describe line mapping information, and some of the issues caused by compiler optimizations.

> Start with the same example code from the previous article:

> The compiler only includes the line mapping information when the code is compiled with debugging information enabled (the -g option):

gemini.tuxmachines.org