#dylanlang — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dylanlang, aggregated by home.social.
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
In going through some old papers, I ran across these very interesting documents from long ago that I can't seem to find public reference to. They seem to offer some important historical insight about the Dylan language. This is from back when Dylan was called Ralph as a working title. In those days, the still-being-designed Lisp-like language had not yet moved to an infix syntax, and it looked and acted more like Scheme with an object system similar in spirit to CLOS (the Common Lisp Object System).
My understanding is that there were some fairly deliberate choices made to NOT target the Lisp or Scheme community as users, which is part of why the move to infix. I think they wanted to appeal to a disaffected C++ crowd, but ultimately lost out to Java for that bid, and then having left the Lisp user base behind, ended up with a very small community as a result.
But I still think there could be things the Scheme community would want to glean from this snapshot of history.
I've included a scan of an email proposal I got from Dave Moon while he and I were at Symbolics, with his proposal for how to add conditions to the language. Note that Dylan did eventually go public and did have a condition system, so you could also just study that design directly. But what's useful here is to see how all that looked syntactically in a Scheme-like syntax. But, in that regard, I recommend starting by looking at the language itself.
[0] Ralph: A Dynamic Language with Efficient Application Delivery, by Andrew LM Shalit, July 25, 1991.
https://nhplace.com/kent/History/dylan/ralph-1991-07-25.pdf[1] Ralph Conditions (part 1 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-1-of-2-1991-08-14.pdf[2] Ralph Conditions (part 2 of 2)
https://nhplace.com/kent/History/dylan/ralph-moon-conditions-proposal-v1.1-part-2-of-2-1991-08-14.pdfcc @sigue @ramin_hal9001 @screwlisp
#DylanLang #RalphLang #ComputerHistory #Harlequin #Lisp #CommonLisp #ConditionSystem #ConditionHandling #ErrorSystem #Scheme #SchemeLang #CLOS #AppleHistory #KentsHistoryProject
-
@sigue #RabbitSeason ? #DuckSeason ? Noo, #DylanLang season.
-
Un día alegre.
#Dylanlang tiene una nueva versión https://opendylan.org/release-notes/2025.1.html en la que modestamente he participado.
Muchas gracias a los Dylan #hackers que me dejan jugar en este lenguaje de #programación. -
In 2024/Jan/31 I did a PR to #github to add a .gitignore for #DylanLang. Two days ago a bot told me that this PR is staled and it will be close after 180 days of inactivity. I should leave a comment if I want to keep it open.
What would you do?
-
> #DylanLang has separate functions for map, map-as, and do.
That is certainly a justifiable different design approach (than #CommonLisp's).
-
CW: BIKE-SHEDDING
In Dylan, the IF expression looks like this:
if (test)
true-expr
else
false-expr
end(The true/false expressions can be any number of expressions but here I'm interested in the short case.)
Generally I'm quite happy with this, but when there are a lot of very short conditionals in a function it can get too verbose.
I have a macro that looks like this for such cases:
iff(test, true-expr, false-expr)
What should I call it?!
-
Comments from the .proto file are now carried over to the .dylan file, and add-foo methods are created for repeated fields.
https://github.com/cgay/protocol-buffers/blob/main/sources/descriptor-pb.dylan
-
Comments from the .proto file are now carried over to the .dylan file, and add-foo methods are created for repeated fields.
https://github.com/cgay/protocol-buffers/blob/main/sources/descriptor-pb.dylan
-
Comments from the .proto file are now carried over to the .dylan file, and add-foo methods are created for repeated fields.
https://github.com/cgay/protocol-buffers/blob/main/sources/descriptor-pb.dylan
-
This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)
https://github.com/cgay/protocol-buffers/commit/bf084b35eb2d11230ed8e83b60cc6cbae7d733ea
-
This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)
https://github.com/cgay/protocol-buffers/commit/bf084b35eb2d11230ed8e83b60cc6cbae7d733ea
-
This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)
https://github.com/cgay/protocol-buffers/commit/bf084b35eb2d11230ed8e83b60cc6cbae7d733ea
-
This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)
https://github.com/cgay/protocol-buffers/commit/bf084b35eb2d11230ed8e83b60cc6cbae7d733ea
-
This commit contains the generated code for descriptor.proto. Dylan protobufs are now bootstrapped! (But lots more work to do.)
https://github.com/cgay/protocol-buffers/commit/bf084b35eb2d11230ed8e83b60cc6cbae7d733ea
-
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 -
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 -
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 -
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 -
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
-
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
-
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
-
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
-
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
-
@Shou @ntnsndr @Paul030 @christina
I'm also very much interested in establishing a #LispCoop, that is, a #cooperative of #freelancer|s focused on projects involving programming languages in the #FamilyOfLisp.
The motivation is that #SoftwareDevelopment & #ProjectManagement need to observe sufficiently different aims, practices, paradigms and risks with #Lisp programming languages.
🌺
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt -
@Shou @ntnsndr @Paul030 @christina
I'm also very much interested in establishing a #LispCoop, that is, a #cooperative of #freelancer|s focused on projects involving programming languages in the #FamilyOfLisp.
The motivation is that #SoftwareDevelopment & #ProjectManagement need to observe sufficiently different aims, practices, paradigms and risks with #Lisp programming languages.
🌺
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt -
@Shou @ntnsndr @Paul030 @christina
I'm also very much interested in establishing a #LispCoop, that is, a #cooperative of #freelancer|s focused on projects involving programming languages in the #FamilyOfLisp.
The motivation is that #SoftwareDevelopment & #ProjectManagement need to observe sufficiently different aims, practices, paradigms and risks with #Lisp programming languages.
🌺
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt -
@Shou @ntnsndr @Paul030 @christina
I'm also very much interested in establishing a #LispCoop, that is, a #cooperative of #freelancer|s focused on projects involving programming languages in the #FamilyOfLisp.
The motivation is that #SoftwareDevelopment & #ProjectManagement need to observe sufficiently different aims, practices, paradigms and risks with #Lisp programming languages.
🌺
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt -
@Shou @ntnsndr @Paul030 @christina
I'm also very much interested in establishing a #LispCoop, that is, a #cooperative of #freelancer|s focused on projects involving programming languages in the #FamilyOfLisp.
The motivation is that #SoftwareDevelopment & #ProjectManagement need to observe sufficiently different aims, practices, paradigms and risks with #Lisp programming languages.
🌺
🦎 https://telegram.me/FamilyOfLisp
🦎 https://matrix.to/#/#family-of-lisp:magdeburg.jetzt -
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
On #Friendica and #Telegram:
›Call for Papers — 16th European #Lisp Symposium — #ELSConf —#Amsterdam — 2023-04-24/25‹
🔗 Friendica: https://libranet.de/display/0b6b25a8-1763-a88a-e526-72b275177682
🦎 Telegram: https://t.me/FamilyOfLisp/309
🌺
🏷️ #CommonLisp #Scheme #EmacsLisp #Clojure #Racket #ACL2 #AutoLisp #ISLISP #DylanLang #SKILL #Hy #Shen #Carp #Janet #Jank #uLisp #Picolisp #Gamelisp #TXR #FunctionalProgramming #AMOP #SICP #CLOS #PAIP #CLtL2 #AIMA #Emacs #VIM #LispWorks #AllegroCommonLisp #ACL #CLISP #SBCL #MetaObject #MetaObjectSystem
-
On #Friendica:
›The extended form of the Common Lisp <loop> macro as a Controlled Natural Language (CNL)‹
🔗 https://libranet.de/display/0b6b25a8-1963-a776-9fb1-d9c503592537
🌺
🏷️ #InterLisp #CommonLisp #ControlledNaturalLanguage #DylanLang #ELSConf #VIM #Emacs #PrettyPrinting #functional #hashtable #iteration #loop #dotimes #dolist #maphash #map #with·hashtable·iterator #Scheme #Macro #CommonLisp #ControlledNaturalLanguage #CNL #ComputerAidedProgramming #CAP
-
On #Friendica:
›The extended form of the Common Lisp <loop> macro as a Controlled Natural Language (CNL)‹
🔗 https://libranet.de/display/0b6b25a8-1963-a776-9fb1-d9c503592537
🌺
🏷️ #InterLisp #CommonLisp #ControlledNaturalLanguage #DylanLang #ELSConf #VIM #Emacs #PrettyPrinting #functional #hashtable #iteration #loop #dotimes #dolist #maphash #map #with·hashtable·iterator #Scheme #Macro #CommonLisp #ControlledNaturalLanguage #CNL #ComputerAidedProgramming #CAP
-
On #Friendica:
›The extended form of the Common Lisp <loop> macro as a Controlled Natural Language (CNL)‹
🔗 https://libranet.de/display/0b6b25a8-1963-a776-9fb1-d9c503592537
🌺
🏷️ #InterLisp #CommonLisp #ControlledNaturalLanguage #DylanLang #ELSConf #VIM #Emacs #PrettyPrinting #functional #hashtable #iteration #loop #dotimes #dolist #maphash #map #with·hashtable·iterator #Scheme #Macro #CommonLisp #ControlledNaturalLanguage #CNL #ComputerAidedProgramming #CAP
-
If you would like to come over to a friendly group on Telegram focused on the programming languages in the #FamilyOfLisp — please feel welcomed to join!
We are here:
🌺
🏷️ #Lisp #Scheme #CommonLisp #Racket #InterLisp #Clojure #BaLindaLisp #Hy #ELSConf #ZetaLisp #LispMachine #ConnectionMachine #ThinkingMachines #Emacs #AutoLisp #CLOS #AMOP #SICP #CLtL2 #PAIP #AIMA #PCL #Symbolics #Genera #DylanLang #LFE #ISLisp #Arc #Janet #Jank #OnLisp #HTDP #CLHS #EuLisp
-
If you would like to come over to a friendly group on Telegram focused on the programming languages in the #FamilyOfLisp — please feel welcomed to join!
We are here:
🌺
🏷️ #Lisp #Scheme #CommonLisp #Racket #InterLisp #Clojure #BaLindaLisp #Hy #ELSConf #ZetaLisp #LispMachine #ConnectionMachine #ThinkingMachines #Emacs #AutoLisp #CLOS #AMOP #SICP #CLtL2 #PAIP #AIMA #PCL #Symbolics #Genera #DylanLang #LFE #ISLisp #Arc #Janet #Jank #OnLisp #HTDP #CLHS #EuLisp
-
If you would like to come over to a friendly group on Telegram focused on the programming languages in the #FamilyOfLisp — please feel welcomed to join!
We are here:
🌺
🏷️ #Lisp #Scheme #CommonLisp #Racket #InterLisp #Clojure #BaLindaLisp #Hy #ELSConf #ZetaLisp #LispMachine #ConnectionMachine #ThinkingMachines #Emacs #AutoLisp #CLOS #AMOP #SICP #CLtL2 #PAIP #AIMA #PCL #Symbolics #Genera #DylanLang #LFE #ISLisp #Arc #Janet #Jank #OnLisp #HTDP #CLHS #EuLisp