home.social

#amop — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #amop, aggregated by home.social.

  1. Vassil Nikolov | Васил Николов @[email protected] ·

    (1) I second that.
    _The Art of the Metaobject Protocol_ is a beautiful book.
    A masterclass.
    Pure magic.

    (2) I am partial to Allen's _The Anatomy of Lisp_.
    I claim that its essence is good and valuable.
    (If you read it, you have to abstract away that it uses Lisp as it was in the now rather distant past.)
    I understood what a continuation is from this book (which presents a continuation "merely" as a register in an abstract Lisp machine).

    (3) The first edition of _Common Lisp: the Language_ can be reconstructed from the second edition, but there is aesthetic value in having the first edition itself.

    #AMOP
    #AnatomyOfLisp
    #ArtOfTheMetaobjectProtocol
    #CLtL
    #CommonLispTheLanguage
    #Lisp

    @zyd @spnw

    #amop #anatomyoflisp #artofthemetaobjectprotocol #cltl #commonlispthelanguage #lisp
  2. Vassil Nikolov | Васил Николов @[email protected] ·

    (1) I second that.
    _The Art of the Metaobject Protocol_ is a beautiful book.
    A masterclass.
    Pure magic.

    (2) I am partial to Allen's _The Anatomy of Lisp_.
    I claim that its essence is good and valuable.
    (If you read it, you have to abstract away that it uses Lisp as it was in the now rather distant past.)
    I understood what a continuation is from this book (which presents a continuation "merely" as a register in an abstract Lisp machine).

    (3) The first edition of _Common Lisp: the Language_ can be reconstructed from the second edition, but there is aesthetic value in having the first edition itself.

    #AMOP
    #AnatomyOfLisp
    #ArtOfTheMetaobjectProtocol
    #CLtL
    #CommonLispTheLanguage
    #Lisp

    @zyd @spnw

    #amop #anatomyoflisp #artofthemetaobjectprotocol #cltl #commonlispthelanguage #lisp
  3. Vassil Nikolov | Васил Николов @[email protected] ·

    (1) I second that.
    _The Art of the Metaobject Protocol_ is a beautiful book.
    A masterclass.
    Pure magic.

    (2) I am partial to Allen's _The Anatomy of Lisp_.
    I claim that its essence is good and valuable.
    (If you read it, you have to abstract away that it uses Lisp as it was in the now rather distant past.)
    I understood what a continuation is from this book (which presents a continuation "merely" as a register in an abstract Lisp machine).

    (3) The first edition of _Common Lisp: the Language_ can be reconstructed from the second edition, but there is aesthetic value in having the first edition itself.

    #AMOP
    #AnatomyOfLisp
    #ArtOfTheMetaobjectProtocol
    #CLtL
    #CommonLispTheLanguage
    #Lisp

    @zyd @spnw

    #lisp #commonlispthelanguage #cltl #artofthemetaobjectprotocol #anatomyoflisp #amop
  4. Vassil Nikolov | Васил Николов @[email protected] ·

    (1) I second that.
    _The Art of the Metaobject Protocol_ is a beautiful book.
    A masterclass.
    Pure magic.

    (2) I am partial to Allen's _The Anatomy of Lisp_.
    I claim that its essence is good and valuable.
    (If you read it, you have to abstract away that it uses Lisp as it was in the now rather distant past.)
    I understood what a continuation is from this book (which presents a continuation "merely" as a register in an abstract Lisp machine).

    (3) The first edition of _Common Lisp: the Language_ can be reconstructed from the second edition, but there is aesthetic value in having the first edition itself.

    #AMOP
    #AnatomyOfLisp
    #ArtOfTheMetaobjectProtocol
    #CLtL
    #CommonLispTheLanguage
    #Lisp

    @zyd @spnw

    #amop #anatomyoflisp #artofthemetaobjectprotocol #cltl #commonlispthelanguage #lisp
  5. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    I found [it] interesting since it says their approach should have wide applicability.

    And very rightly so:
    both
    that you should find it interesting
    and
    that the approach should have wide applicability.

    Just making my opinion explicit, not that present or absent company needs me to know that 🙂.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  6. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    I found [it] interesting since it says their approach should have wide applicability.

    And very rightly so:
    both
    that you should find it interesting
    and
    that the approach should have wide applicability.

    Just making my opinion explicit, not that present or absent company needs me to know that 🙂.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #metaobjectprotocol #amop
  7. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    I found [it] interesting since it says their approach should have wide applicability.

    And very rightly so:
    both
    that you should find it interesting
    and
    that the approach should have wide applicability.

    Just making my opinion explicit, not that present or absent company needs me to know that 🙂.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  8. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    I found [it] interesting since it says their approach should have wide applicability.

    And very rightly so:
    both
    that you should find it interesting
    and
    that the approach should have wide applicability.

    Just making my opinion explicit, not that present or absent company needs me to know that 🙂.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  9. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    I found [it] interesting since it says their approach should have wide applicability.

    And very rightly so:
    both
    that you should find it interesting
    and
    that the approach should have wide applicability.

    Just making my opinion explicit, not that present or absent company needs me to know that 🙂.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  10. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    "Metaobject protocols: Why we want them and what else they can do"
    Gregor Kiczales, J.Michael Ashley, Luis Rodriguez, Amin Vahdat, and Daniel G. Bobrow
    ... 1993

    Excellent catch.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  11. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    "Metaobject protocols: Why we want them and what else they can do"
    Gregor Kiczales, J.Michael Ashley, Luis Rodriguez, Amin Vahdat, and Daniel G. Bobrow
    ... 1993

    Excellent catch.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #metaobjectprotocol #amop
  12. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    "Metaobject protocols: Why we want them and what else they can do"
    Gregor Kiczales, J.Michael Ashley, Luis Rodriguez, Amin Vahdat, and Daniel G. Bobrow
    ... 1993

    Excellent catch.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  13. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    "Metaobject protocols: Why we want them and what else they can do"
    Gregor Kiczales, J.Michael Ashley, Luis Rodriguez, Amin Vahdat, and Daniel G. Bobrow
    ... 1993

    Excellent catch.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  14. Vassil Nikolov | Васил Николов @[email protected] ·

    <"/>
    "Metaobject protocols: Why we want them and what else they can do"
    Gregor Kiczales, J.Michael Ashley, Luis Rodriguez, Amin Vahdat, and Daniel G. Bobrow
    ... 1993

    Excellent catch.

    #AMOP
    #MetaObjectProtocol

    @dougmerritt

    #amop #metaobjectprotocol
  15. Vassil Nikolov | Васил Николов @[email protected] ·

    > I shortened Jim des Rivieres to Rivieres. Is this correct, or am I meant to write des Rivieres?

    I would keep "des" and more importantly I would check what the already established practice for citing this name is in the literature.
    That would also include keeping the accent (des Rivières).

    #AMOP
    #CommonLisp
    #MetaobjectProtocol

    @screwlisp

    #amop #commonlisp #metaobjectprotocol
  16. Vassil Nikolov | Васил Николов @[email protected] ·

    > I shortened Jim des Rivieres to Rivieres. Is this correct, or am I meant to write des Rivieres?

    I would keep "des" and more importantly I would check what the already established practice for citing this name is in the literature.
    That would also include keeping the accent (des Rivières).

    #AMOP
    #CommonLisp
    #MetaobjectProtocol

    @screwlisp

    #metaobjectprotocol #commonlisp #amop
  17. Vassil Nikolov | Васил Николов @[email protected] ·

    > I shortened Jim des Rivieres to Rivieres. Is this correct, or am I meant to write des Rivieres?

    I would keep "des" and more importantly I would check what the already established practice for citing this name is in the literature.
    That would also include keeping the accent (des Rivières).

    #AMOP
    #CommonLisp
    #MetaobjectProtocol

    @screwlisp

    #amop #commonlisp #metaobjectprotocol
  18. Vassil Nikolov | Васил Николов @[email protected] ·

    > I shortened Jim des Rivieres to Rivieres. Is this correct, or am I meant to write des Rivieres?

    I would keep "des" and more importantly I would check what the already established practice for citing this name is in the literature.
    That would also include keeping the accent (des Rivières).

    #AMOP
    #CommonLisp
    #MetaobjectProtocol

    @screwlisp

    #amop #commonlisp #metaobjectprotocol
  19. Vassil Nikolov | Васил Николов @[email protected] ·

    > I shortened Jim des Rivieres to Rivieres. Is this correct, or am I meant to write des Rivieres?

    I would keep "des" and more importantly I would check what the already established practice for citing this name is in the literature.
    That would also include keeping the accent (des Rivières).

    #AMOP
    #CommonLisp
    #MetaobjectProtocol

    @screwlisp

    #amop #commonlisp #metaobjectprotocol
  20. Vassil Nikolov | Васил Николов @[email protected] ·

    [Applying the Metaobject Protocol.]

    Needless to say, if you not only read that book, but also put it to use, you will learn a lot and that is priceless.

    What you describe seems like a suitable problem to apply the MOP to and to get a grasp of it.
    Good hunting!

    #AMOP
    #CommonLisp
    #MetaobjectProtocol
    #MOP

    @screwlisp @dougmerritt

    #amop #commonlisp #metaobjectprotocol #mop
  21. Vassil Nikolov | Васил Николов @[email protected] ·

    [Applying the Metaobject Protocol.]

    Needless to say, if you not only read that book, but also put it to use, you will learn a lot and that is priceless.

    What you describe seems like a suitable problem to apply the MOP to and to get a grasp of it.
    Good hunting!

    #AMOP
    #CommonLisp
    #MetaobjectProtocol
    #MOP

    @screwlisp @dougmerritt

    #mop #metaobjectprotocol #commonlisp #amop
  22. Vassil Nikolov | Васил Николов @[email protected] ·

    [Applying the Metaobject Protocol.]

    Needless to say, if you not only read that book, but also put it to use, you will learn a lot and that is priceless.

    What you describe seems like a suitable problem to apply the MOP to and to get a grasp of it.
    Good hunting!

    #AMOP
    #CommonLisp
    #MetaobjectProtocol
    #MOP

    @screwlisp @dougmerritt

    #amop #commonlisp #metaobjectprotocol #mop
  23. Vassil Nikolov | Васил Николов @[email protected] ·

    [Applying the Metaobject Protocol.]

    Needless to say, if you not only read that book, but also put it to use, you will learn a lot and that is priceless.

    What you describe seems like a suitable problem to apply the MOP to and to get a grasp of it.
    Good hunting!

    #AMOP
    #CommonLisp
    #MetaobjectProtocol
    #MOP

    @screwlisp @dougmerritt

    #amop #commonlisp #metaobjectprotocol #mop
  24. Vassil Nikolov | Васил Николов @[email protected] ·

    [Applying the Metaobject Protocol.]

    Needless to say, if you not only read that book, but also put it to use, you will learn a lot and that is priceless.

    What you describe seems like a suitable problem to apply the MOP to and to get a grasp of it.
    Good hunting!

    #AMOP
    #CommonLisp
    #MetaobjectProtocol
    #MOP

    @screwlisp @dougmerritt

    #amop #commonlisp #metaobjectprotocol #mop
  25. Vassil Nikolov | Васил Николов @[email protected] ·

    [AMOP]
    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.

    Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  26. Vassil Nikolov | Васил Николов @[email protected] ·

    [AMOP]
    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.

    Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.

    #AMOP
    #CLOS
    #CommonLisp

    #commonlisp #clos #amop
  27. Vassil Nikolov | Васил Николов @[email protected] ·

    [AMOP]
    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.

    Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  28. Vassil Nikolov | Васил Николов @[email protected] ·

    [AMOP]
    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.

    Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  29. Vassil Nikolov | Васил Николов @[email protected] ·

    [AMOP]
    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    Right now I'm thinking that the real value of _The Art of the Metaobject Protocol_ is showing one way to do metaprogramming, and object-oriented programming is merely a demonstration domain.

    Of course, what begat AMOP was a desire for an approach that can cover a large part of the OOP language design space, not just one point in that space, in order to be attractive to different schools of thought.

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  30. Vassil Nikolov | Васил Николов @[email protected] ·

    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    > no one else has been mentioning (so far as I've noticed) "The Art of the Metaobject Protocol"

    Not in this thread.
    Indeed, this book is a tour de force (et de magique).

    > uncertain that the topic deserved such a deep analysis

    The topic—maybe, maybe not, but the book is really about the metatopic, i.e. about metaprogramming, if I may abuse this prefix.
    (I know this ought to be formulated more carefully.)

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  31. Vassil Nikolov | Васил Николов @[email protected] ·

    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    > no one else has been mentioning (so far as I've noticed) "The Art of the Metaobject Protocol"

    Not in this thread.
    Indeed, this book is a tour de force (et de magique).

    > uncertain that the topic deserved such a deep analysis

    The topic—maybe, maybe not, but the book is really about the metatopic, i.e. about metaprogramming, if I may abuse this prefix.
    (I know this ought to be formulated more carefully.)

    #AMOP
    #CLOS
    #CommonLisp

    #commonlisp #clos #amop
  32. Vassil Nikolov | Васил Николов @[email protected] ·

    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    > no one else has been mentioning (so far as I've noticed) "The Art of the Metaobject Protocol"

    Not in this thread.
    Indeed, this book is a tour de force (et de magique).

    > uncertain that the topic deserved such a deep analysis

    The topic—maybe, maybe not, but the book is really about the metatopic, i.e. about metaprogramming, if I may abuse this prefix.
    (I know this ought to be formulated more carefully.)

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  33. Vassil Nikolov | Васил Николов @[email protected] ·

    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    > no one else has been mentioning (so far as I've noticed) "The Art of the Metaobject Protocol"

    Not in this thread.
    Indeed, this book is a tour de force (et de magique).

    > uncertain that the topic deserved such a deep analysis

    The topic—maybe, maybe not, but the book is really about the metatopic, i.e. about metaprogramming, if I may abuse this prefix.
    (I know this ought to be formulated more carefully.)

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  34. Vassil Nikolov | Васил Николов @[email protected] ·

    @dougmerritt @weekend_editor @sigue @abuseofnotation @screwlisp

    > no one else has been mentioning (so far as I've noticed) "The Art of the Metaobject Protocol"

    Not in this thread.
    Indeed, this book is a tour de force (et de magique).

    > uncertain that the topic deserved such a deep analysis

    The topic—maybe, maybe not, but the book is really about the metatopic, i.e. about metaprogramming, if I may abuse this prefix.
    (I know this ought to be formulated more carefully.)

    #AMOP
    #CLOS
    #CommonLisp

    #amop #clos #commonlisp
  35. Jörg Preisendörfer @[email protected] ·

    ›They Have Played Us #Programmer|s for Absolute #Fool|s‹

    🧷 youtube.com/watch?v=QTiAWZ1Yfz

    🌺

    🏷️ #Lisp #Scheme #CommonLisp #CPP #Rust #DennisRitchie #BrianKernighan #BjarneStroustrup #CLang #Rustacean #MetaProgramming #Risitas #JohnMcCarthy #Unix #Pipes #Segfault #NullPointer #UndefinedBehaviour #GarbageCollection #MemoryManagement #BellLabs #ObjectSystem #FunctionalProgramming #Syntax #Rustaceans #MemorySafety #ElRisitas #CLOS #AMOP

    #programmer #fool #lisp #scheme #commonlisp #cpp
  36. Jörg Preisendörfer @[email protected] ·

    ›They Have Played Us #Programmer|s for Absolute #Fool|s‹

    🧷 youtube.com/watch?v=QTiAWZ1Yfz

    🌺

    🏷️ #Lisp #Scheme #CommonLisp #CPP #Rust #DennisRitchie #BrianKernighan #BjarneStroustrup #CLang #Rustacean #MetaProgramming #Risitas #JohnMcCarthy #Unix #Pipes #Segfault #NullPointer #UndefinedBehaviour #GarbageCollection #MemoryManagement #BellLabs #ObjectSystem #FunctionalProgramming #Syntax #Rustaceans #MemorySafety #ElRisitas #CLOS #AMOP

    #programmer #fool #lisp #scheme #commonlisp #cpp
  37. Jörg Preisendörfer @[email protected] ·

    ›They Have Played Us #Programmer|s for Absolute #Fool|s‹

    🧷 youtube.com/watch?v=QTiAWZ1Yfz

    🌺

    🏷️ #Lisp #Scheme #CommonLisp #CPP #Rust #DennisRitchie #BrianKernighan #BjarneStroustrup #CLang #Rustacean #MetaProgramming #Risitas #JohnMcCarthy #Unix #Pipes #Segfault #NullPointer #UndefinedBehaviour #GarbageCollection #MemoryManagement #BellLabs #ObjectSystem #FunctionalProgramming #Syntax #Rustaceans #MemorySafety #ElRisitas #CLOS #AMOP

    #programmer #fool #lisp #scheme #commonlisp #cpp
  38. Jörg Preisendörfer @[email protected] ·

    ›They Have Played Us #Programmer|s for Absolute #Fool|s‹

    🧷 youtube.com/watch?v=QTiAWZ1Yfz

    🌺

    🏷️ #Lisp #Scheme #CommonLisp #CPP #Rust #DennisRitchie #BrianKernighan #BjarneStroustrup #CLang #Rustacean #MetaProgramming #Risitas #JohnMcCarthy #Unix #Pipes #Segfault #NullPointer #UndefinedBehaviour #GarbageCollection #MemoryManagement #BellLabs #ObjectSystem #FunctionalProgramming #Syntax #Rustaceans #MemorySafety #ElRisitas #CLOS #AMOP

    #amop #clos #elrisitas #memorysafety #rustaceans #syntax
  39. Jörg Preisendörfer @[email protected] ·

    ›They Have Played Us #Programmer|s for Absolute #Fool|s‹

    🧷 youtube.com/watch?v=QTiAWZ1Yfz

    🌺

    🏷️ #Lisp #Scheme #CommonLisp #CPP #Rust #DennisRitchie #BrianKernighan #BjarneStroustrup #CLang #Rustacean #MetaProgramming #Risitas #JohnMcCarthy #Unix #Pipes #Segfault #NullPointer #UndefinedBehaviour #GarbageCollection #MemoryManagement #BellLabs #ObjectSystem #FunctionalProgramming #Syntax #Rustaceans #MemorySafety #ElRisitas #CLOS #AMOP

    #programmer #fool #lisp #scheme #commonlisp #cpp
  40. Jörg Preisendörfer @[email protected] ·

    @Seanleblanc

    WRT #CommonLisp Object System (#CLOS):

    The seminal book ›The Art of the Metaobject protocol‹ (1991, #AMOP) by #Kiczales, #Rivieres & #Bobrow demonstrates & discusses many design patterns for #ObjectSystem|s with #metaobject protocol, in which methods are not part of classes, due to #multimethod, #multipledispatch paradigms.

    It also contributed much to #DylanLang.

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Lisp #FamilyOfLisp #CLtL2 #CLHS #ELSConf #XEROXParc

    #commonlisp #clos #amop #kiczales #rivieres #bobrow
  41. Jörg Preisendörfer @[email protected] ·

    @Seanleblanc

    WRT #CommonLisp Object System (#CLOS):

    The seminal book ›The Art of the Metaobject protocol‹ (1991, #AMOP) by #Kiczales, #Rivieres & #Bobrow demonstrates & discusses many design patterns for #ObjectSystem|s with #metaobject protocol, in which methods are not part of classes, due to #multimethod, #multipledispatch paradigms.

    It also contributed much to #DylanLang.

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Lisp #FamilyOfLisp #CLtL2 #CLHS #ELSConf #XEROXParc

    #commonlisp #clos #amop #kiczales #rivieres #bobrow
  42. Jörg Preisendörfer @[email protected] ·

    @Seanleblanc

    WRT #CommonLisp Object System (#CLOS):

    The seminal book ›The Art of the Metaobject protocol‹ (1991, #AMOP) by #Kiczales, #Rivieres & #Bobrow demonstrates & discusses many design patterns for #ObjectSystem|s with #metaobject protocol, in which methods are not part of classes, due to #multimethod, #multipledispatch paradigms.

    It also contributed much to #DylanLang.

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Lisp #FamilyOfLisp #CLtL2 #CLHS #ELSConf #XEROXParc

    #commonlisp #clos #amop #kiczales #rivieres #bobrow
  43. Jörg Preisendörfer @[email protected] ·

    @Seanleblanc

    WRT #CommonLisp Object System (#CLOS):

    The seminal book ›The Art of the Metaobject protocol‹ (1991, #AMOP) by #Kiczales, #Rivieres & #Bobrow demonstrates & discusses many design patterns for #ObjectSystem|s with #metaobject protocol, in which methods are not part of classes, due to #multimethod, #multipledispatch paradigms.

    It also contributed much to #DylanLang.

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Lisp #FamilyOfLisp #CLtL2 #CLHS #ELSConf #XEROXParc

    #xeroxparc #elsconf #clhs #cltl2 #familyoflisp #lisp
  44. Jörg Preisendörfer @[email protected] ·

    @Seanleblanc

    WRT #CommonLisp Object System (#CLOS):

    The seminal book ›The Art of the Metaobject protocol‹ (1991, #AMOP) by #Kiczales, #Rivieres & #Bobrow demonstrates & discusses many design patterns for #ObjectSystem|s with #metaobject protocol, in which methods are not part of classes, due to #multimethod, #multipledispatch paradigms.

    It also contributed much to #DylanLang.

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Lisp #FamilyOfLisp #CLtL2 #CLHS #ELSConf #XEROXParc

    #commonlisp #clos #amop #kiczales #rivieres #bobrow
  45. Jörg Preisendörfer @[email protected] ·

    @freakazoid

    Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

    🧷 plover.com/~mjd/misc/hbaker-ar

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

    #henrygbaker #lisp #scheme #commonlisp #elsconf #clojure
  46. Jörg Preisendörfer @[email protected] ·

    @freakazoid

    Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

    🧷 plover.com/~mjd/misc/hbaker-ar

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

    #henrygbaker #lisp #scheme #commonlisp #elsconf #clojure
  47. Jörg Preisendörfer @[email protected] ·

    @freakazoid

    Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

    🧷 plover.com/~mjd/misc/hbaker-ar

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

    #henrygbaker #lisp #scheme #commonlisp #elsconf #clojure
  48. Jörg Preisendörfer @[email protected] ·

    @freakazoid

    Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

    🧷 plover.com/~mjd/misc/hbaker-ar

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

    #autolisp #emacs #clisp #sbcl #clozure #cltl2
  49. Jörg Preisendörfer @[email protected] ·

    @freakazoid

    Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?

    🧷 plover.com/~mjd/misc/hbaker-ar

    🌺

    🦎 telegram.me/FamilyOfLisp
    🦎 matrix.to/#/#family-of-lisp:ma

    🏷️ #Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp

    #henrygbaker #lisp #scheme #commonlisp #elsconf #clojure
  50. Jörg Preisendörfer @[email protected] ·

    40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:

    🧷 (Friendica) libranet.de/display/0b6b25a8-1

    🦎 (Matrix) matrix.to/#/!gqlYAZsfzSnmFNEHA

    🦎 (Telegram) telegram.me/FamilyOfLisp/309

    🌺

    🏷️ #Lisp #Scheme #CommonLisp #Clojure #Racket #Emacs #ACL2 #AutoLisp # ISLisp #DylanLang #SKILL #Hy #Shen #Carp #Janet #uLisp #Picolisp #Gamelisp #TXR #InterLisp #Medley #OpenGenera #Symbolics #ThinkingMachines #ConnectionMachine #MultiLisp #AMOP #CLOS #SICP #PAIP #AIMA #Lambda #CLtL2 #HTDP

    #europeanlispsymposium #elsconf #amsterdam #lisp #scheme #commonlisp