And how is OOP useful?
Is CLOS still worth learning?
Well, it is integrated into Common Lisp, so if you want to master Common Lisp and read other people's Common Lisp code, you should learn CLOS. Some important libraries such as the Hunchentoot web server (used by this website's pastebin) are written using many CLOS features.
https://en.wikipedia.org/wiki/Common_Lisp_Object_System#Literature has a good list of resources for learning CLOS. The typically recommended book for an introduction to CLOS is Object-Oriented Programming in Common Lisp: A Programmer's Guide to CLOS by Sonya E. Keene.
https://en.wikipedia.org/wiki/Object-Oriented_Programming_in_Common_Lisp
What problem are you trying to solve?
CLOS is one of the great features of Common Lisp. If you're writing Common Lisp, you need to understand CLOS because it's widely used.
It's useful if the problem you are trying to solve benefits from structured data. But it's also totally different from Java/sepples style OOP
>>4
Why is C++ known as "sepples"?
>>5
C to SE
PLUS-PLUS to PP
MULTIPLES to LES
it sounds like a disease
it sounds like a disease
Could be worse: aCePooP.
In languages like java, OOP is often used as a hack to make up for lack of language functionality. The result is very boilerplate-looking code. However that does not mean that OOP itself is worthless. CLOS in my opinion provides you with oop in the shape of a handy tool, with a focus on what the compiler can do to make your life easier rather than philosophical issues. Even just for that I think it's worth taking a look at. Things that perplex c++ and java programmers for years, like the visitor design pattern, become obvious once you learn what double dispatching is through CLOS
>>6
CPPOOP