It's 2023, so of course I'm learning Common Lisp

Re:It's 2023, so of course I'm learning Common Lisp by lispm on Thursday July 27, 2023 @04:42AM (#36890671)

> It works in code compiled from c++ too: define and associate a signal handler for sigkill, call a function whose symbol can't be runtime resolved by the linker, sigkill is sent and caught, define your function (in your asm dejure), patch the GOT to point from the original symbol to wherever the bytearray is with your asm, and voila.

I don't need to do anything like that in Lisp. I just define the function and RESUME THE COMPUTATION WHERE IT STANDS in my read eval print loop. << important parts in uppercase.

[ Parent | on HN ]

Re:It's 2023, so of course I'm learning Common Lisp by mathisfun123 on Thursday July 27, 2023 @04:44AM (#36890690)

Do you think the magic fairies are doing it for you? Your interpreter/runtime is still doing it whether you're aware of it or not.

My point is very simple: I can do it too, in any language I want, and so there's nothing special about lisp.

[ Parent | on HN ]

Re:It's 2023, so of course I'm learning Common Lisp by kgwgk on Thursday July 27, 2023 @05:20AM (#36890972)

https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule

[ Parent | on HN ]

Re:It's 2023, so of course I'm learning Common Lisp by lispm on Thursday July 27, 2023 @04:53AM (#36890761)

> My point is very simple: I can do it too, in any language I want, and so there's nothing special about lisp.

The big difference is: "I can do it too" means YOU need to do it. Lisp does it for me already, I have not to do anything. I don't want to know what you claim you can do with C++, show me where C++ does it for you.

Telling me "I can do it too" is not a good answer. Show me where the language implementation (!) does it for you.

[ Parent | on HN ]