@ramin_hal9001 @kentpitman @screwlisp I used to have so much fun playing with the condition system in Common Lisp some years ago. Can't wait to use this in Chicken Scheme or Guile Scheme 
Discussion
Loading...
@ramin_hal9001 @kentpitman @screwlisp I used to have so much fun playing with the condition system in Common Lisp some years ago. Can't wait to use this in Chicken Scheme or Guile Scheme
@momo cool!
Well then, please have a listen to the episodes of the #LispyGopherClimate podcast that me, @kentpitman and @screwlisp did these past few weeks:
- Kent Pitman presents his lisp condition system implemented for python
- Kent Pitman, Scott Zimmermann, Ramin Honary, Screwlisp: Lisp Conditions in Python
- Common Lisp condition handling lore
- Common Lisp condition system, code review of my programming example
- Common Lisp condition handling w/ Kent Pitman, Ramin Honary
#tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme
@ramin_hal9001 @screwlisp @momo
Cringe. When you list them out like that it makes me feel like people must surely be sick of me hogging all that space. 😊 I hope if others have things to say on these topics that they'll talk our host to have them on instead. Really it's quite an achievement just to fill an hour every week and keep the forum going, so I'm just stopping by to do my part to help with that effort, I really try to not be as self-important as that list makes me look.
@kentpitman ha ha, sorry! To be fair, our discussions of the past few weeks has centered around a programming system which is credited in large part to you.
I’ll tell you what, I’ll remove your name from items 3 and 4, it won’t change the description of the episode that much.
@ramin_hal9001 @screwlisp @momo
Well, I think it's fine for you to make your own choices as you see fit. I just needed to blush aloud.
I think I've said this on the air but it bears repeating: There are many stories I held back telling for many years because I thought them not mine to tell. I thought others would tell them. But some people left us, and some are not public speakers or writers, and maybe some didn't have the perspective to see they should be speaking. So eventually I realized I needed to speak for and about others, but I try to emphasize that these topics are community efforts and that many ideas attributed to me are really at best a framing of ideas that I had a hand in, but that were inspired by others' work.
Alas, I already talk long and those little stories about how things came to be only make me take longer to say things, at a time when I wish I were speaking shorter. My haiku writing is a kind of apology for that fact, to show I CAN focus and write short sometimes. But I think it's important in the case of the topics I talk about that people not think they are the output of one brilliant (not me) person on one day doing something, at least not intentionally. People DO sometimes do things that accidentally persist but it's not always the things they think in the moment will. What matters is to put in good energy every day on things that matter to you and hope that something will survive, and to not get too self-assured that you yourself are what's holding things together.
So I hope when my name comes up that people see I'm really just trying to speak for the whole community, not just the one for which I had formal title for a brief while, but just the mix of interesting ideas and concepts that I've been lucky enough to see others do. Where possible I mention who I got ideas from, but in many cases I don't even remember and I lament that. Once in a while I think it's my idea, but even there I'm probably just misremembering an influence. Still, it's the mix of topics and ideas that is important, and so I love it when others join in and mix it up because that's all it ever was in the first place and that's what needs to be continued.
@kentpitman @ramin_hal9001
and thanks for your participation both of you and everyone else.
Kent, I do think you are seen as having a particular outreach role in the language having authored the pitmanual, taken over as editor from Kathy Chapman for ANSI common lisp, written ANSI CL's hyperspec, standardised ISLISP, and contributed to other specs and standards as well as having worked in lisp in Macsyma and the usual lisp companies.
2+ more replies (not shown)
@ramin_hal9001 @kentpitman @screwlisp @momo I will stick with the original.