[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.
@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.)
›They Have Played Us #Programmer|s for Absolute #Fool|s‹
https://www.youtube.com/watch?v=QTiAWZ1YfzI&t=217s
#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
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.
https://telegram.me/FamilyOfLisp https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
Regarding the publications of #HenryGBaker on #Lisp and related topics — have you had a look around here?
https://www.plover.com/~mjd/misc/hbaker-archive/home.html
https://telegram.me/FamilyOfLisp https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
#Scheme #CommonLisp #ELSConf #Clojure #DylanLang #CLHS #Lisp #FamilyOfLisp #Racket #AMOP #CLOS #CLtL2 #Clozure #SBCL #CLISP #Emacs #AutoLisp
40 days left to the submission deadline of #EuropeanLispSymposium (#ELSConf) in #Amsterdam:
(Friendica) https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
(Matrix) https://matrix.to/#/!gqlYAZsfzSnmFNEHAT:magdeburg.jetzt/$z7kGECRQluF1iZzNhW-0I1e3lUmg-pff8PcAh96gox4
(Telegram) https://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
The #Telegram and #Matrix groups named #FamilyOfLisp are now synchronized (bridged):
https://telegram.me/FamilyOfLisp
https://matrix.to/#/#family-of-lisp:magdeburg.jetzt
The two groups are for friendly exchange and dialogue on topics related to the Family of #Lisp #programming languages.
#Scheme #CommonLisp #Racket #Clojure #DylanLang #ELSConf #AMOP #CLOS #InterLisp #OpenGenera #LispMachine #Medley #ConnectionMachine #Symbolics #AutoLisp #MacLisp #ZetaLisp #EuLisp #ISLisp #CLHS #SICP #AIMA #CLtL2 #PAIP #HTDP
Note that the #PrettyPrinting dispatch tables of #CommonLisp conceptionally are a #GenericFunction with #ParametricDispatch.
The function SET-PPRINT-DISPATCH is essentially an ADD-METHOD to the pretty printing parametric dispatch.
(Unfortunatly, the canonical, #ProofOfConcept implementation of PP by #RichardWaters is one single convoluted mess; basically a negative example of software design, even by standards of its time.)
I am guilty of combining #FunctionalProgramming with the #CommonLisp Object System. 
What will my fate be? 
