What makes Lisp Lisp?

I found this last text repetitive and boring, I think I had understood where Lisp came from and almost everything there was to know about its story in the previous readings and podcasts. The only part of the reading I found interesting was the eval definition function where they showed you how to write the Lisp interpreter in Lisp. The thing with programming using a functional language is that is a complete flip of paradigm, when the data is also the code and you need to differentiate it using quotes.
One of the difference I found in this reading regarding Lisp and Clojure is that in Lisp the empty list represents false and the atom t represents true where as in Clojure we have true to represent true and false or nil to represent false. Also, I noted the differences between the primitive functions in Clojure and in Lisp, where in Lisp they are called weird and in Clojure they have the name of what they do. This last I noted since the podcast about Lisp that explained why the functions where called weirdly in Lisp. The amazing thing about Lisp is that all is made out from seven primitive forms which are quote (to indicate which things must be ignored or not evaluated), atom (which is to see if it is a list or just an element), eq (to evaluate if two things are equal), car (to return the first element of a list), cdr (to return all but the first element of a list), cons (to append things to a list) and cond (to evaluate true or false statements). 
So in Lisp we have a very small language which can grow to a complex one as needed by the programmer. With those primitive elements and the list as primary data structure, you can construct a functional language which can adjust to the need of any programmer. That is what I found in the reading.

Comentarios

Publicar un comentario

Entradas más populares de este blog

Two is more than double of one

This week's reading talks about pair programming, a software development practice in which two developers work at the same time in the same project in the same thing in order to keep track of the work in case one misses. But it also improves times, productivity and software quality. The reading's goal is to facilitate the transition to pair programming by explaining how you already know how to do it. The text begins explaining how pair programming in the XP methodology for development is really successful and how programmers attribute the success of their productivity and the methodology to the technique. And although many programmers tend to work alone and resit to the change, most of them  succeed in the transition to pair programming and begin loving it. The first rule of pair programming is Share everything, even mistakes. The second one is play fair, meaning that you shall not take the control of the development and let the other person also be the one who codes. The thi
Leer más

Is really functional programming better?

Since the beginning of software development, we have used the same programing techniques, the author mentions that this is because it “closely resembles how a computer works at the hardware level: the processor fetches data from memory, performs elementary opera- tions on it, and writes the result back to a memory cell” (Hinsen, 2009). The only different technique that has been developed is functional programming, which was developed as a mathematical theory first and then into a programming language called LISP. So, we have two different approaches: functional programming and imperative programming.   Functional programming consists on composing functions for computations, just as previously mentioned, this paradigm was first a mathematical theory and thus a function is “a mapping from input values to output values” (Hinsen, 2009) not to be confused with subroutines. A big difference between functions from functional programming and from imperative programming is that functional fu
Leer más