Skip to main content

Lisp: Hackable by Default


I'm watching the MIT lectures for the Structure and Interpretation of Computer Programs which my buddy Mike Cheponis was nice enough to give to me. I noticed a few interesting things.

In C, it's common to write "x->a". x is a pointer to a struct with a member a. In Lisp, you'd write (a x). a is a function that operates on some object x in order to return a value. That means that, by default, "a" has some "wiggle room" to do something special because it's a function. That's why in Java, the norm is to use getters and setters for everything. It provides "wiggle room" which I also call "hackability". In languages like Python, Ruby, and C#, "x.a" might or might not be an actual function call because those languages support properties. Depending on the details, in languages with inheritance, you might even say there's an extra dimension of hackability. For instance, in Java, x.getA() might be extended by subclasses.

One of the lectures covered symbolic manipulation of algebraic expressions. That means writing a system that can recognize that "(+ x x)" is the same as "(* x 2)". The professor had a procedure make-sum. "(make-sum x y)" is pretty straightforward. Under the covers, it returns "(list '+ x y)". However, he showed that there's no reason make-sum shouldn't be smarter. For instance "(make-sum x 0)" should really just return x. Internally, I was thinking of make-sum as a Java-like constructor for some class named Sum. However, a Java constructor can't just return x. It has to return an instance of the Sum class. Hence, if you were coding this in Java, you wouldn't use a constructor. You would use a static method that returns an Expression, where Expression is some interface. My point is that in Lisp make-sum is just a constructor, and constructors in Lisp by default have the freedom to return an instance of whatever they want. That means they're hackable by default.

I have one more thing I'd like to mention. Look at the image. This was filmed in 1986. First of all, it's amazing to me that something filmed 22 years ago is still very interesting and relevant to me today. It's even more amazing to consider that Lisp started in 1958. However, what's intriguing is that there are several women in the class. Not just one or two, but several. Where'd all the women go? There are so few female programmers these days.

Comments

Shawn W. said…
This comment has been removed by the author.
Shawn W. said…
(reposted with a working link)

Thought I'd post a link to the video series:

http://swiss.csail.mit.edu/classes/6.001/abelson-sussman-lectures/
Anonymous said…
Yes. There are much more women in computer science classes than working in the software industry... You can check http://www.devchix.com
jjinux said…
> Thought I'd post a link to the video series:

Very helpful. Thanks!
Anonymous said…
When i was watching these classes it happened frequently that individuals of the audience looked a bit "displaced". Not interested, not able to follow, maybe just tired. After all it was however produced for internal company use originally (HP IIRC). No company video without propaganda.. therefore it would make sense to include as many minorities of that time in this specific industry. And then we have it.. ;-)
Anonymous said…
>However, a Java constructor can't just return x. It has to return an instance of the Sum class. Hence, if you were coding this in Java, you wouldn't use a constructor.

Bjarne Stroustrup discusses a similar scenario for implementing efficient matrix multiplication in C++ in section 22.4.7 of "The C++ Programming Language, Third Edition". He winds up defining overloaded operators that return auxilary classes representing computations to be performed. He sums it up by saying:

"This technique is based on the idea of using compile-time analysis and closure objects to transfer evaluation of subexpression into an object representing a composite operation. It can be applied to a variety of problems with the common attribute that several pieces of information need to be gathered into one function before evaluation can take place. I refer to the objects generated to defer evaluation as composition closure objects or simply compositors."

Popular posts from this blog

Ubuntu 20.04 on a 2015 15" MacBook Pro

I decided to give Ubuntu 20.04 a try on my 2015 15" MacBook Pro. I didn't actually install it; I just live booted from a USB thumb drive which was enough to try out everything I wanted. In summary, it's not perfect, and issues with my camera would prevent me from switching, but given the right hardware, I think it's a really viable option. The first thing I wanted to try was what would happen if I plugged in a non-HiDPI screen given that my laptop has a HiDPI screen. Without sub-pixel scaling, whatever scale rate I picked for one screen would apply to the other. However, once I turned on sub-pixel scaling, I was able to pick different scale rates for the internal and external displays. That looked ok. I tried plugging in and unplugging multiple times, and it didn't crash. I doubt it'd work with my Thunderbolt display at work, but it worked fine for my HDMI displays at home. I even plugged it into my TV, and it stuck to the 100% scaling I picked for the othe

ERNOS: Erlang Networked Operating System

I've been reading Dreaming in Code lately, and I really like it. If you're not a dreamer, you may safely skip the rest of this post ;) In Chapter 10, "Engineers and Artists", Alan Kay, John Backus, and Jaron Lanier really got me thinking. I've also been thinking a lot about Minix 3 , Erlang , and the original Lisp machine . The ideas are beginning to synthesize into something cohesive--more than just the sum of their parts. Now, I'm sure that many of these ideas have already been envisioned within Tunes.org , LLVM , Microsoft's Singularity project, or in some other place that I haven't managed to discover or fully read, but I'm going to blog them anyway. Rather than wax philosophical, let me just dump out some ideas: Start with Minix 3. It's a new microkernel, and it's meant for real use, unlike the original Minix. "This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code.&quo

Haskell or Erlang?

I've coded in both Erlang and Haskell. Erlang is practical, efficient, and useful. It's got a wonderful niche in the distributed world, and it has some real success stories such as CouchDB and jabber.org. Haskell is elegant and beautiful. It's been successful in various programming language competitions. I have some experience in both, but I'm thinking it's time to really commit to learning one of them on a professional level. They both have good books out now, and it's probably time I read one of those books cover to cover. My question is which? Back in 2000, Perl had established a real niche for systems administration, CGI, and text processing. The syntax wasn't exactly beautiful (unless you're into that sort of thing), but it was popular and mature. Python hadn't really become popular, nor did it really have a strong niche (at least as far as I could see). I went with Python because of its elegance, but since then, I've coded both p