Internals of GCC

The article makes a quick walk trough around the process that involves the compilation, same that is reiterated that must be known by the programmers, not because of it's imperative to understand every detail of the process, but the focus of the interview in this topic goes to the notion of the base of the modern programming is on the shoulders of the compilers and it's phases. Not understanding compilers isn't bad, but it's necessary for us to know at least the bases.

I found amazing the way that the interviewee talks about the GNU compiler collection as he does, showing us the effort that was made for making it the most flexible and portable, making it compatible to many of the OS, and the focus that is for giving every input as text to convert it into a generic document that will became machine code for it's executing. This reflex for us the amount and importance of the work that it's done for the actual programming languages to progress.

This article then starts to get very repetitive in many aspects but let's us see that this kind of work for developing a compiler needs a lot of efforts and I think of it as a non recognizable work between programmers, or at least I've never heard the phrase "Oh, I want to become a compiler programmer" or any similar in my generation. This kind of publications gave me a little more conscious about the enormous labor that takes for our actual conception of the programming careers and jobs to exist. The evolution that has been given in the last 30 or 40 years, just for gave us the possibility of things like the globalization, but the angular stone for this is shown in this podcast, as simple as it could seem, and I'm more interested in this topic with this things.

Comentarios

Entradas más populares de este blog

Introduction

The Hundred-Year Language

Making Compiler Design Relevant for Students who will (most likely) Never Design a Compiler