Making a Compiler Design
At first glance learning about compiler design sound fun due to the challenge it represents because it sounds really hard, but at the same time interesting.Learning about how it works and the techniques that it uses in order to make things easier, it sounds even more interesting as it is the philosophy of dividing and conquering that it is one of the angular stones of all programming.
I also like the story the author used to describe how having a particular way of thinking about this sort of problems can be transferred into other areas of thinking and as a result it opens a bunch of opportunities to improve my programming skills, as wells as learn new ways to solve complex problems with little code and ingenious solutions.
I am super excited to begin learning said techniques and I have big expectations about this techniques to put them into practice for my jobs and personal projects to see what functions better and what worse.
Because at the moment of writing this post I don’t understand a bunch of principles that the article mentions, or simply I don’t see how they are useful or how to implement them.
For instance tokenisation when doing the lexical analysis of the compilation process that results in looking for errors.
I mean, I get what the purpose is, however I can’t seem to get my head around on how to do it correctly. As a language has many different ways to do a same operation. And regex might check for them, however it just seems to detect the existence or non-existence of something, maybe, but I think a more rigorous analysis of the syntax is need in order for it to be really reliable and trust-worthy.
Like I said, I have big expectations because it seems like a challenge.
I also like the story the author used to describe how having a particular way of thinking about this sort of problems can be transferred into other areas of thinking and as a result it opens a bunch of opportunities to improve my programming skills, as wells as learn new ways to solve complex problems with little code and ingenious solutions.
I am super excited to begin learning said techniques and I have big expectations about this techniques to put them into practice for my jobs and personal projects to see what functions better and what worse.
Because at the moment of writing this post I don’t understand a bunch of principles that the article mentions, or simply I don’t see how they are useful or how to implement them.
For instance tokenisation when doing the lexical analysis of the compilation process that results in looking for errors.
I mean, I get what the purpose is, however I can’t seem to get my head around on how to do it correctly. As a language has many different ways to do a same operation. And regex might check for them, however it just seems to detect the existence or non-existence of something, maybe, but I think a more rigorous analysis of the syntax is need in order for it to be really reliable and trust-worthy.
Like I said, I have big expectations because it seems like a challenge.
Comentarios
Publicar un comentario