libera/#commonlisp - IRC Chatlog
Search
10:50:32
scymtym
by now, c++ has real compile-time evaluation for a (growing) subset of the language in addition to templates: https://en.cppreference.com/w/cpp/language/constexpr
11:21:08
younder
C++ also has ambitions to throw away C headers. In 2026 the language might have lambda's ready for generic thread execution. Kinda the same we has had in Lisp with lparelell since 2015 or so.
12:27:34
jiny
in emacs slime debug how can I continue with different value that caused an error? I see it in bactrace 0: ..
12:30:31
beach
... and it is not related to SLIME. It is what the author of the code chose to signal.
12:31:48
decweb
If you're the author of the code, there are some convenenience forms like `check-type` which will signal restartable conditions, and might at least introduce you to the topic and you can look at its code.
12:33:01
beach
jiny: If you replace your BREAK by a CHECK-TYPE as decweb suggests, then you can alter the value in the debugger.
12:35:29
beach
jiny: And notice that the type given to check-type can be very specific, e.g., (NOT (EQL 234)).
12:38:24
jiny
thank you. i'm looking into https://www.lispworks.com/documentation/HyperSpec/Body/m_check_.htm that sounds like far beyond my level.
12:39:41
beach
jiny: It is not hard. If you have a variable FOO that takes on the value 234 and you don't want that, instead of (BREAK), write (CHECK-TYPE FOO (NOT (EQL 234)))
12:44:35
beach
jiny: So if you receive an odd number but you want it to be even, then use the type (SATISFIES EVENP).
12:49:30
scymtym
it is also possible to restart function calls (key r) or force function calls to return (key R) for a subset of all function calls on the stack (not just the top one). calls for which this is possible are highlighted by SLIME (in green by default, i think)
12:52:57
scymtym
(restarting function calls will not undo any side effects so detailed knowledge about the functions in question is required)
15:11:17
nij-
Q. provide, require, *module* are all deprecated. What should I use instead in vanilla CL (e.g. if it doesn't have asdf).
16:27:53
bike
all the non-implementation-defined parts of provide and require do is put something on the *modules* list, and LOAD a file if the module hasn't already been added, respectively
18:07:01
nij-
In the convention, a single semicolon denotes the start of a single line comment, appended after a line of code.
18:07:29
nij-
However, I saw in many places where people use a slightly stricter rule. I wonder if that's conventional.
18:09:16
younder
A double semicolon is a in function comment. triple semicolon a data structure comment and four semicolons file comment. All semicolons more than one fill a entire line.
18:17:29
younder
I'd use a space after ; because I think it's more readable. But I don't see and rule written in stone anywhere.
18:24:06
younder
Remember Lispers pride themselves in how terse CL is if we were to indent like Java.. it would hardly seem shorter ;)
18:26:40
nij-
gilberth - https://novaspec.org/ Seeing only one entry on this page.. makes me wondering.. will there be more specs coming up (in principle, no hurries)?