phoe-krk

57 ms·

781.
by phoe-krk 6y ago
For the fourth day in a row, there are thousands on the streets in all major Polish cities and a lot of smaller ones. Protests and city blockages have already been announced for tomorrow.
782.
by phoe-krk 6y ago
Hope that you enjoy the read!
783.
by phoe-krk 6y ago
Dylan! (Which is commonly called a Lisp dialect due to its internal structure, even though it lacks homoiconicity.) See https://opendylan.org/documentation/intro-dylan/conditions.h... There are implementations of
784.
by phoe-krk 6y ago
> good catch Ouch. Kudos for the pun, that was truly awful. :D
785.
by phoe-krk 6y ago
Thank you! I hope that it serves you well.
786.
by phoe-krk 6y ago
Because I was unable to add the submission - I was instead redirected to https://news.ycombinator.com/item?id=21656268 .
787.
Gitlab was down(status.gitlab.com)
68 points by phoe-krk 6y ago|31 comments
788.
by phoe-krk 6y ago
McCLIM is not a domain of archaeology anymore; it has been seeing lots of development recently[0]. As for demonstrating it, two of the recent Online Lisp Meeting[1] videos utilize McCLIM: one of them describes Clouseau, an inspector applica
789.
by phoe-krk 6y ago
I have been doing desktop applications using Qtools[0] which is relatively pleasant to work with. I have prepared a hello-world kind of Qtools project[1] that is automatically built and released into ZIP files using Travis CI. (I haven&#x27
790.
by phoe-krk 6y ago
I'm glad they've finally been proposed, as ugly as they need to be in Python. It's not even about full homoiconicity; a language which is capable of easily understanding its own symbolic representation along with quote/
791.
by phoe-krk 6y ago
I actually don't know this. Java creators were well aware of Common Lisp when they were working on Java (the famous quote from Guy Steele, "We were after the C++ programmers. We managed to drag a lot of them about halfway to Lisp.
792.
by phoe-krk 6y ago
Thank you; I hope that I will find and allocate enough time in the nearby future to help with maintaining CCL some more.
793.
by phoe-krk 6y ago
Yes, this last fact is explicitly mentioned in the last two sentences of this section. > Another issue is preserving the state of the program stack, as it is destroyed in the process of dumping the Lisp image, and it cannot be fully res
794.
by phoe-krk 6y ago
Could you link me to any sources for that GCC behavior? Also, if we can have dynamically established handlers, then we could also have dynamically established restarts (even if by means of a dynamic variable implemented via a lexical variab
795.
by phoe-krk 6y ago
I see. I know that it is possible to transform primitive CL control flow operators into CPS, as it is shown on https://gitlab.common-lisp.net/cl-cont/cl-cont/-/blob/master... , so I assume that it is also
796.
by phoe-krk 6y ago
Yes, I'm implying that. For instance, a lot of Python's use of "throw" is not really because we want to signal an exception in some Python code, we just want to unwind the stack while passing some values and we can'
797.
by phoe-krk 6y ago
Thanks, hope that it serves you well.
798.
by phoe-krk 6y ago
Oh golly. To think that people would quote my own words to answer Hacker News questions... (Thanks for the assist!)
799.
by phoe-krk 6y ago
I haven't explored the CPS topic deeply, so I cannot really answer. As far as I understand, CPS preserves the state of the program or stack information by storing it in closures that are ready to be called at any time, whereas a condit
800.
by phoe-krk 6y ago
Thank you for the congrats, and the fact that it wasn't described anywhere is the reason for my original frustration, which in turn is the reason why this book exists. I hope that the book is useful for you; in case of any questions, p
801.
by phoe-krk 6y ago
Thank you. I am taking a big risk by making the statement in 4.11 (in the online Appendix E), since it directly implies that none of C++, Java, Python et al actually do any exception handling at all . It's all control flow, always has
802.
by phoe-krk 6y ago
I sincerely hope that my book aids this problem that you are speaking of - both by allowing programmers and implementers of other languages use the techniques that originate in Lisp, and to try and bash at the Lisp-as-a-meme prejudice that
803.
by phoe-krk 6y ago
Thanks for the assist! I have one comment: > The equivalent of `finally`/destructors is `unwind-protect`, which has to interoperate with the condition mechanism but doesn't deal with conditions itself. It actually doesn'
804.
by phoe-krk 6y ago
It is the latter. It is possible to implement a condition system on top of any language that has dynamic variables, a `finally`-style construct and some mechanism for unwinding the stack. Since dynamic variables are implementable on top of
805.
by phoe-krk 6y ago
Both. The book contains an explanation of how to derive the condition system from the primitive operators of Common Lisp, which should be useful both for users that try to gain some intuition or broaden their understanding of how the condit
806.
by phoe-krk 6y ago
Not exactly. The Common Lisp condition system is usable for handling error situations, but it's usable for much more as well; the act of signaling a condition does not immediately unwind the stack, like throwing an exception does, and
807.
by phoe-krk 6y ago
Thanks. The only thing that is sad to me is that this content did not make it into the book itself. (I guess that I can be proud of myself though: the first edition of the book wasn't even out of production and I already had some stuff
808.
Show HN: My book, The Common Lisp Condition System(amazon.com)
177 points by phoe-krk 6y ago|61 comments
809.
by phoe-krk 6y ago
Author here. The Common Lisp Condition System is my first book and it was previously discussed on Hacker News[0] as soon as the Apress page for the book was first posted. The HN discussion was very fruitful and insightful and prompted me
810.
by phoe-krk 6y ago
Yes, got it - thank you for the response.

More ›