freenode/#sbcl - IRC Chatlog
Search
9:23:55
jdz
dra: This does not seem to be an SBCL-specific question (and of course expecting people to watch youtube videos as an offer of problem context is offensive). But assuming you're talking about global variables read on about DEFPARAMETER and DEFVAR.
9:32:00
jdz
dra: It is up to you to spend as much time necessary to minimize the time others have to spend when trying to answer your questions. So the usual "when I do this, I get that, whereas I expected something else; my reading of this and that resource seem to support my expectation, so what am I missing" is the way to go. Also advertisements are offensive in general.
10:51:18
luis
Is it possible to distinguish files with WARNINGs vs files with SB-C:COMPILER-ERRORs from COMPILE-FILE's return values or should I use HANDLER-BIND?
10:54:35
luis
dra: there was some discussion on sbcl-devel about getting rid of that annoying warning.
11:02:11
dra
Where I'm coming from here: In On Lisp, chapter 20, Graham uses a top-level (setq *cont* #'identity) to create a global lexical variable. And in the video above Weitz writes (setq foo 13) seemingly without DEFVAR'ing it first but he doesn't get a warning.
11:03:28
luis
dra: a workaround might be something like (defmacro :set (symbol value) `(setf (symbol-value ,'symbol) ,value)), then use (:set foo 13)
11:04:05
luis
dra: (setq *cont* ...) is silly though, since the *earmuff* convention suggests it should be a special variable.
11:06:16
luis
dra: I've placed that macro in the keyword package (which is something you should avoid in general) because I find it convenient to place debugging utilities there. Other people might disagree with (or even be offended by) this. ;-)
11:09:25
dra
luis: Well, any time you call one of those keyword-interned macros a (: appears in your code. So your convention makes me happy!
14:26:13
MetaYan
dra: Have you seen the "p. 267" paragraph at http://www.paulgraham.com/onlisperrata.html ?
14:54:57
dra
MetaYan: Ah, yes I had seen it before. Thanks. But it's still a lexical global which, technically, doesn't exist in CL, right?
18:37:25
Posterdati
I installed sbcl-2.0.1-threads on OpenBSD 6.7 amd64 and there's no :openbsd key in *features*... How can be possible?
19:57:43
Posterdati
sbcl --noinform --no-userinit --eval '(progn (print (remove-if-not (lambda (feature) (search "BSD" (symbol-name feature))) *features*)) (terpri))' --quit ==> (:BSD)
20:43:17
stassats
2.0.1 is not the latest version, you need to try the latest version before reporting a problem