3 ms·
It depends on what you mean by "object-oriented". A Lisp with no formal OOP system still has objects: conses, strings, symbols. These are nicely abstracted: th
by kazinator 8y ago
It depends on what you mean by "object-oriented".
A Lisp with no formal OOP system still has objects: conses, strings, symbols. These are nicely abstracted: they are defined by operations which construct, access and otherwise manipulate them. These entities have an identity (which we can test with eq) and carry a type. They can move around freely in the program.
There is genericity without OOP: features like car working not only on a cons cell, but also on the nil object. Or length calculating the length of a vector, string or list.
All of this stands in contrast to a procedural paradigm in which there are just storage locations operated on by code, having whatever type the code believes them to have. (Algol 68, Fortran 66, C).
- mimixco 8y agoI think OOPS as a paradigm is pretty well defined without my laying it out. The facts are that Lisp did not have OOPS at the beginning but it's easy to add, and that's one of the greatest strengths of Lisp as a programming language. You can build any programming concepts from modern languages that you want -- but you aren't constrained by any of them.