Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Common Lisp Object System
open-in-new
<h2 id="features">Features</h2> <p>The basic building blocks of CLOS are <a href="/facts/Method_(computer_programming)/8kAXxVYs">methods</a>, <a href="/facts/Class_(computer_programming)/zvzkSAtE">classes</a>, instances of those classes, and <a href="/facts/Generic_function/ulkL9u3G">generic functions</a>. CLOS provides macros to define those: defclass, defmethod, and defgeneric. Instances are created with the method make-instance. </p><p>Classes can have multiple <a href="/facts/Superclass_(computer_science)/a7R1xv8n">superclasses</a>, a list of slots (member variables in C++/Java parlance) and a special <a href="/facts/Metaclass/qIUSeeLa">metaclass</a>. Slots can be allocated by class (all instances of a class share the slot) or by instance. Each slot has a name and the value of a slot can be accessed by that name using the function slot-value. Additionally special generic functions can be defined to write or read values of slots. Each slot in a CLOS class must have a unique name. </p><p>CLOS is a <a href="/facts/Multiple_dispatch/eCYSSjGE">multiple dispatch</a> system. This means that <a href="/facts/Method_(computer_science)/8kAXxVYs">methods</a> can be specialized upon any or all of their required arguments. Most OO languages are single-dispatch, meaning that methods are only specialized on the first argument. Another unusual feature is that methods do not "belong" to classes; classes do not provide a namespace for generic functions or methods. Methods are defined separately from classes, and they have no special access (e.g. "this", "self", or "protected") to class slots. </p><p>Methods in CLOS are grouped into <a href="/facts/Generic_function/ulkL9u3G">generic functions</a>. A generic function is an object which is callable like a function and which associates a collection of methods with a shared name and argument structure, each specialized for different arguments. Since Common Lisp provides non-CLOS classes for structures and built-in data types (numbers, strings, characters, symbols, ...), CLOS dispatch works also with these non-CLOS classes. CLOS also supports dispatch over individual objects (eql specializers). CLOS does not by default support dispatch over all Common Lisp data types (for example dispatch does not work for fully specialized array types or for types introduced by deftype). However, most Common Lisp implementations provide a <a href="/facts/Metaobject_protocol/UgJq5A0t">metaobject protocol</a> which allows generic functions to provide application specific specialization and dispatch rules. </p><p>Dispatch in CLOS is also different from most OO languages: </p> <ol><li>Given a list of arguments, a list of applicable methods is determined.</li> <li>This list is sorted according to the specificity of their parameter specializers.</li> <li>Selected methods from this list are then combined into an effective method using the method combination used by the generic function.</li> <li>The effective method is then called with the original arguments.</li></ol> <p>This dispatch mechanism works at runtime. Adding or removing methods thus may lead to changed effective methods (even when the generic function is called with the same arguments) at runtime. Changing the method combination also may lead to different effective methods. </p><p>For example, </p> ; Declare the common argument structure prototype. (defgeneric f (x y)) ; Define an implementation for (f integer y), where y matches all types. (defmethod f ((x integer) y) 1) (f 1 2.0) => 1 ; Define an implementation for (f integer real). (defmethod f ((x integer) (y real)) 2) (f 1 2.0) => 2 ; Dispatch changed at runtime. <p>Like the OO systems in most <a href="/facts/Dynamic_programming_language/j8cQm8RF">dynamic languages</a>, CLOS does not enforce <a href="/facts/Encapsulation_(computer_science)/kzDnbHPe">encapsulation</a>. Any slot can be accessed using the slot-value function or via (optionally auto-generated) <a href="/facts/Accessor_method/sKfxYzFM">accessor methods</a>. To access it via slot-value you have to know the name of the slot. CL programmers use the language's <a href="/facts/Namespace/9efXwMtV">package</a> facility to declare which functions or data structures are intended for export. </p><p>Apart from normal ("primary") methods, there also are :before, :after, and :around "auxiliary" methods. The former two are invoked prior to, or after the primary method, in a particular order based on the class hierarchy. An :around method can control whether the primary method is executed at all. Additionally, the programmer can specify whether all possible primary methods along the <a href="/facts/Hierarchy_(object-oriented_programming)/a7R1xv8n">class hierarchy</a> should be called or just the one providing the closest match. </p><p>The <i>Standard Method-Combination</i> provides the primary, before, after and around methods explained above. There are other Method-Combinations with other method types. New (both simple and complex) Method-Combinations and method types can be defined. </p><p>CLOS allows <a href="/facts/Multiple_inheritance/kFvNb9rY">multiple inheritance</a>. When the default order in which methods are executed in multiple inheritance is not correct, the programmer may resolve the <a href="/facts/Diamond_problem/kFvNb9rY">diamond inheritance problems</a> by specifying the order of method combinations. </p><p>CLOS is dynamic, meaning that not only the contents, but also the <i>structure</i> of its objects can be modified at runtime. CLOS supports changing class definitions on-the-fly (even when instances of the class in question already exist) as well as changing the class membership of a given instance through the change-class operator. CLOS also allows one to add, redefine and remove methods at runtime. The <a href="/facts/Circle-ellipse_problem/dsHw7hDI">Circle-Ellipse Problem</a> is readily solved in CLOS, and most OOP <a href="/facts/Design_pattern_(computer_science)/mV7r4egw">design patterns</a> either disappear or are qualitatively simpler.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> </p><p>CLOS is not a <a href="/facts/Prototype-based_language/x9oNIYPG">prototype language</a>: classes must be defined before objects can be instantiated as members of that class. </p> <h2 id="metaobject-protocol">Metaobject Protocol</h2> <p>Outside of the ANSI Common Lisp standard, there is a widely implemented extension to CLOS called the <a href="/facts/Metaobject/UgJq5A0t">Metaobject</a> Protocol (MOP). The MOP defines a standard interface to the underpinnings of the CLOS implementation, treating classes, slot-descriptions, generic-functions and methods themselves as instances of <a href="/facts/Metaclass/qIUSeeLa">metaclasses</a>, and allows the definition of new metaclasses and the modification of all CLOS behavior. The flexibility of the CLOS MOP prefigures <a href="/facts/Aspect-oriented_programming/HK7CFwan">aspect-oriented programming</a>, which was later developed by some of the same engineers, such as <a href="/facts/Gregor_Kiczales/68UI7JEn">Gregor Kiczales</a>. The MOP defines the behavior of the whole object system by a set of protocols. These are defined in terms of CLOS. Thus it is possible to create new object-systems by extending or changing the provided CLOS functionality. The book <a href="/facts/The_Art_of_the_Metaobject_Protocol/rKTGw68G">The Art of the Metaobject Protocol</a> describes the use and implementation of the CLOS MOP. </p><p>The various Common Lisp implementations have slightly different support for the Meta-Object Protocol. The <i>Closer</i><a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> project aims to provide the missing features. </p> <h2 id="influences-from-older-lisp-based-object-systems">Influences from older Lisp-based object systems</h2> <p><a href="/facts/Flavors_(programming_language)/fAXYuuc7">Flavors</a> (and its successor New Flavors) was the object system on the MIT <a href="/facts/Lisp_Machine/8ULEHdF0">Lisp Machine</a>. Large parts of the Lisp Machine operating systems and many applications for it use Flavors or New Flavors. Flavors introduced <a href="/facts/Multiple_inheritance/kFvNb9rY">multiple inheritance</a> and <a href="/facts/Mixins/QHG68mgY">mixins</a>, among other features. Flavors is mostly obsolete, though implementations for Common Lisp do exist. Flavors was using the message passing paradigm. New Flavors introduced generic functions. </p><p><a href="/facts/CommonLoops/q03T0Lgv">CommonLoops</a> was the successor of LOOPS (from Xerox <a href="/facts/Interlisp/zSEUS17z">Interlisp</a>-D). CommonLoops was implemented for Common Lisp. A portable implementation called Portable CommonLoops (PCL) was the first implementation of CLOS. PCL is widely ported and still provides the base for the CLOS implementation of several <a href="/facts/Common_Lisp/mq1pRbSF">Common Lisp</a> implementations. PCL is implemented mostly in portable Common Lisp with only a few system dependent parts. </p> <h2 id="clos-in-other-programming-languages">CLOS in other programming languages</h2> <p>Because of the power and expressivity of CLOS, as well as the historical availability of Tiny CLOS (a simplified portable CLOS implementation written by <a href="/facts/Gregor_Kiczales/68UI7JEn">Gregor Kiczales</a> for use with Scheme), CLOS-like MOP-based object systems have become the <i>de facto</i> norm in most Lisp dialect implementations, as well as finding their way into some other languages' <a href="/facts/Object-oriented_programming/TxNMEcao">OOP</a> facilities: </p> <ul><li>COS, the C Object System<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a></li> <li><a href="/facts/Dylan_(programming_language)/VVQGkShF">Dylan</a></li> <li>Dynace, a (largely) CLOS implementation in C<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a></li> <li>EIEIO for Emacs Lisp</li> <li>Gauche, Scheme with CLOS</li> <li>GOOPS in <a href="/facts/GNU_Guile/xsnGWQKV">GNU Guile</a></li> <li>ILOS in <a href="/facts/ISLISP/4qnw7Nyn">ISLISP</a></li> <li>Meroon, an Object System in Scheme</li> <li>Sagittarius, a Scheme with CLOS</li> <li>ScmObj, for Scheme</li> <li>SOS for MIT Scheme</li> <li>STklos, a Scheme with CLOS</li> <li>Swindle in Racket</li> <li>COOPS in Chicken Scheme</li> <li>VCLOS for <a href="/facts/Cadence_SKILL/TF0eqSAm">Skill</a><a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a></li> <li>Tiny CLOS<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a></li> <li>S4 classes in <a href="/facts/S_(programming_language)/VTG29WnE">S</a> and <a href="/facts/R_(programming_language)/LSrkr8K8">R</a> programming languages</li></ul> <h2 id="further-reading">Further reading</h2> <ul><li><a href="/facts/Daniel_G._Bobrow/GKssbwds">Bobrow, Daniel G.</a>; Kahn, Kenneth; <a href="/facts/Gregor_Kiczales/68UI7JEn">Kiczales, Gregor</a>; <a href="/facts/Larry_Masinter/GuKjgjhB">Masinter, Larry</a>; Stefik, Mark; Zdybel, Frank (June 1986). <a href="https://web.archive.org/web/20220817140051/https://interlisp.org/docs/1986-commonloops.pdf">"CommonLoops: Merging Lisp and Object-Oriented Programming"</a> (PDF). <i>Conference proceedings on Object-oriented Programming Systems Languages and Applications</i>. <a href="/facts/OOPSLA/LDchJh3V">OOPSLA</a> '86. pp. 17–29. <a href="/facts/Doi_(identifier)/muM9Etpq">doi</a>:<a href="https://doi.org/10.1145%2F28697.28700">10.1145/28697.28700</a>. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 978-0-89791-204-4. <a href="/facts/S2CID_(identifier)/ldJsHa2Y">S2CID</a> <a href="https://api.semanticscholar.org/CorpusID:62631315">62631315</a>. Archived from <a href="https://interlisp.org/docs/1986-commonloops.pdf">the original</a> (PDF) on 2022-08-17. Retrieved 2022-03-17.</li> <li>Veitch, Jim (1998). "A History and Description of CLOS". In <a href="/facts/Peter_H._Salus/dIJ2EY0f">Salus, Peter H.</a> (ed.). <i>Handbook of Programming Languages, Volume IV: Functional and Logic Programming Languages</i> (1st ed.). Macmillan Technical Publishing. pp. 107–158. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 1-57870-011-6.</li></ul> <h2 id="literature">Literature</h2> <ul><li>Sonya Keene, <i><a href="/facts/Object-Oriented_Programming_in_Common_Lisp%3a_A_Programmer%2527s_Guide_to_CLOS/AcrDGJBb">Object-Oriented Programming in Common Lisp: A Programmer's Guide to CLOS</a></i>, 1988, Addison-Wesley. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-201-17589-4</li> <li><a href="/facts/Gregor_Kiczales/68UI7JEn">Gregor Kiczales</a>, Jim des Rivieres, and <a href="/facts/Daniel_G._Bobrow/GKssbwds">Daniel G. Bobrow</a>, <i><a href="/facts/The_Art_of_the_Metaobject_Protocol/rKTGw68G">The Art of the Metaobject Protocol</a></i>, 1991, MIT Press. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-262-61074-4</li> <li>Jo A. Lawless and Molly M. Miller, <i>Understanding CLOS: the Common Lisp Object System</i>, 1991, Digital Press, <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 1-55558-064-5</li> <li>Andreas Paepcke, <i>Object-Oriented Programming: the CLOS Perspective</i>, 1993, The MIT Press. <a href="/facts/ISBN_(identifier)/15AdSPa9">ISBN</a> 0-262-16136-2</li> <li><a href="http://www.dreamsongs.com/Files/ECOOP.pdf">The Common Lisp Object System: An Overview</a> by <a href="/facts/Richard_P._Gabriel/0N3SGIES">Richard P. Gabriel</a> and Linda DeMichiel provides a good introduction to the motivation for defining classes by means of generic functions.</li> <li><a href="http://cl-cookbook.sourceforge.net/clos-tutorial/">Fundamentals of CLOS</a> by <a href="/facts/Nick_Levine/JqqGqNHP">Nick Levine</a> provides a step-by-step exposure to the implementation of OO concepts in CLOS, and how to utilize them. It is intended for anybody with a basic knowledge of Lisp or Scheme.</li> <li><i><a href="/facts/Common_Lisp_HyperSpec/ybhQQXSA">Common Lisp HyperSpec</a></i>, <a href="http://www.lispworks.com/documentation/HyperSpec/Body/07_.htm">Chapter 7: <i>Objects</i></a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"CLOS is a standard. Multiple vendors supply CLOS. CLOS (or parts of it) is being used to add object-orientation to other Lisp dialects such as EuLisp or Emacs Lisp." p. 110 of Veitch 1998 <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>In the Design Patterns in Dynamic Languages slides, Peter Norvig presents his findings that 16 out of 23 design patterns taken from various textbooks are either "invisible or simpler" in Dylan or Common Lisp than in C++. <a href="http://norvig.com/design-patterns/" target="_blank">http://norvig.com/design-patterns/</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Closer Project: Closer to MOP <a href="http://common-lisp.net/project/closer/closer-mop.html" target="_blank">http://common-lisp.net/project/closer/closer-mop.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>Deniau, Laurent (12 March 2010). The C Object System: Using C as a High-Level Object-Oriented Language (PDF). arXiv:1003.2547. CiteSeerX 10.1.1.763.7946. Retrieved 2022-03-17. <a href="https://ldeniau.web.cern.ch/ldeniau/html/cos-oopsla09-draft.pdf" target="_blank">https://ldeniau.web.cern.ch/ldeniau/html/cos-oopsla09-draft.pdf</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>Dynace Object Oriented Extension To C <a href="https://github.com/blakemcbride/Dynace" target="_blank">https://github.com/blakemcbride/Dynace</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>Newton, Jim; Rhodes, Christophe (28 November 2008). "Custom Specializers in Object-Oriented Lisp". Journal of Universal Computer Science. 14 (20): 3370–3388. CiteSeerX 10.1.1.523.2413. doi:10.3217/jucs-014-20-3370. S2CID 12032836. Retrieved 2022-03-17. <a href="https://www.jucs.org/jucs_14_20/custom_specializers_in_object.html" target="_blank">https://www.jucs.org/jucs_14_20/custom_specializers_in_object.html</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>Tiny CLOS, developed by Gregor Kiczales <a href="http://community.schemewiki.org/?Tiny-CLOS" target="_blank">http://community.schemewiki.org/?Tiny-CLOS</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> </ol>