In the Lisp community @lisp on Lemmy.ml there’s a discussion on what your Lisp development environment looks like and how you got started with Lisp. Of course I’m the weirdo who uses Interlisp as his daily driver.
@AndreasDavour@amoroso@lisp this was done for the Expert System shell Babylon from GMD in Germany. It provided a flexible Frame system, which was built on top of Flavors. There were several Flavor implementations, besides the original one from the Lisp Machine. This MCS is one.
(Flavors was one of the first OOP extensions for Lisp. Classes and message sending. The idea of Mixins came from there. A later version of Flavors was one of the inspirations for CLOS.)
@lispm@amoroso@lisp I like to be reminded of lisp strands like this one from Germany. The conversation can so easily get stuck om what was done at BBN or MIT, while other interesting developments where done elsewhere. For me oop in lisp start and end with clos, but one day I will have to read up on the flavors history.
@amoroso @lisp trying out thephoeron’s version of a Flavors implementation from GMD in two CL systems…
@lispm @amoroso @lisp I wasn’t even aware there was a meta protocol for Flavors! Very interesting!
@AndreasDavour @amoroso @lisp this was done for the Expert System shell Babylon from GMD in Germany. It provided a flexible Frame system, which was built on top of Flavors. There were several Flavor implementations, besides the original one from the Lisp Machine. This MCS is one.
(Flavors was one of the first OOP extensions for Lisp. Classes and message sending. The idea of Mixins came from there. A later version of Flavors was one of the inspirations for CLOS.)
@lispm @amoroso @lisp I like to be reminded of lisp strands like this one from Germany. The conversation can so easily get stuck om what was done at BBN or MIT, while other interesting developments where done elsewhere. For me oop in lisp start and end with clos, but one day I will have to read up on the flavors history.