Compiler Design

This time, we will have double resources related to Rear Admiral Dr. Grace Brewster Murray Hopper. First, we have an articled named Grace Hopper - The mother of Cobol from the l programmer website. Then we have a video documentary named The Queen of Code, directed by Gillian Jacobs.  These are the links to read the article and watch the video. Hope you enjoy them: https://www.i-programmer.info/history/people/294-the-mother-of-cobol.html https://vimeo.com/118556349 In this entry we will talk about a very important woman in computer science, as she was one of the first programmers in history and also she got the name or the title "mother of compilers" because she created the first compiler in the world,  in an era that was very difficult to hold(as a woman). The problem she found at that time was that everyone at their copmuter, programmers had to write different programs depending on the computer they were using. That was the moment she decided to change the way of ho

This time, Internals of GCC is a new type of activity in this course, because now it is not an article to read, it is now a podcast recorded by Software Engineering Radio with Morgan Deters as guest. If you like to hear poadcasts click on the next link to go to the page, tso you can hear it: www.se-radio.net/2007/07/episode-61-internals-of-gcc/. Hope you like it. :) The topic of the poscast is about software engineering, but mainly compiling. The process of it, the parts and what they like about GCC. The speaker starts to talk about how the compiler composes, and he explained that compilers have three parts: front-end, middle-end and back-end, that are the one that translate raw code to trees, optimizes and process all data that has come between all that phases. An important thing that was discussed is that Gcc is a portable compiler that can create different outputs for some processors where the compiler has been used, a powerful strength for GCC, because is capable to compile program

This time, i´'ll talk about "The hundred-year language". an article made by Paul Graham. The main idea of this article, is like to guess how the programming language could be in one hundred years in the future. so, can you imagine how programming language could be in a hundred years or more, from now? Well, that's a really difficult question, because well, we arr talking about predicting future is difficult. People, countries, technogoly and a lot of thing can change in a few years, and when someone puts on the table a hundred years, i cant even imagine. But Paul Graham talks about which language could disappear sooner. A language Paul mention is Java and I've read that Java is slowly dying, so the author could be correct. For a language to "survive", has an option an it is  to combine with another newer. A problem for language, is that they are very slowly to improve because they are not a technology by themselves. An important think Paul mentione