Compiler Design

Hi, today’s entry is going to be a little different. In my other entries and blogs, we were always talking about one article, one podcast, one documentary, etc. But today we are going to talk about two, an article and a mini-documentary. I’m referring to the article “Grace Hopper – The Mother of Cobol” by Historian, and the documentary “The Queen of Code” directed by Gillian Jacobs in 2015. Obviously, they talk about the same topic, in resume Grace Hopper as a programmer.  The first one, the article, talks specifically about Grace Hopper as not only the responsible for the Cobol language development, but also for the constant pressure exerted to the industry for computers development and make them in an accessible way. One of her reasons for this was to bring the research and career woman’s interests in computing to the forefront, why? Because she suffered the disadvantages of being a woman with interest in technology and despite that, she became the most famous and important soft

Hi, this entry will talk about an episode of the Software Engineering Radio. It is Episode 61 and is titled as “Internals of GCC”. The special guest is Morgan Deters and, basically, this podcast talks about compilers and how they internally the work. It covers all the steps of a GNU Compiler Collection construction (in this case GNU), going from parsing different programming languages to machine optimizations and processor binary code generation.  At first, I thought that I would not understand many things in this podcast since I never heard the GCC concept before. Then I started to realize that it could be used to compile C code, or C++ code or even more. This is why I knew that this might be a very robust tool, so I started to expect a good explanation, which came later. The GCC has three parts or aspects: The Front-End, Middle-End and the Back-end. I already heard the first and last term, since I have some experience in web development, but middle-end was new for me.  Basic

Hi, this entry will talk about an article titled: “The Hundred-year language”, written by Paul Graham. Basically, it discusses how computer languages (and programming languages) are going or may be in 100 years.  The author started with a curious and, in my opinion, a great comparison saying that in the same way as species, the languages (including computer or programming languages) form a kind of evolutionary tree, where some of them end as dead-ends branches. A clear example is Cobol that, despite its past popularity, it doesn’t seem to have any descendant, fact that automatically converts it in an evolutionary dead-end branch. I bet that in the great Cobol days, nobody thought that it won’t evolve, nor have descendants, nor be commonly used. Then, the author talked about something really controversial speaking about programming languages: the supposed success of the Java language. I think that Java it’s the most known programming language and for many people the better progra