freenode/lisp - IRC Chatlog
Search
9:29:26
iissaacc
is there any way to quickly get the version of a symbol with the package prefix attached?
9:31:19
phoe
so you cannot always tell from outside which package the symbol + is from, unless you also know the current package
9:32:28
iissaacc
well the problem i have is i convert a symbol to its string representation. Then when it gets converted back into a symbol to be used in funcall it happens in another package, so i get an error saying the function is undefined
9:40:33
phoe
the KEYWORD package is very nice for this because keywords are always printed with the preceding colon (even in package KEYWORD) and because it uses no other package, hence all non-keyword symbols are printed with their package name
9:41:54
phoe
keywords are a singular namespace, and you don't usually want to collide with other people's functions
12:23:25
Xach
i think it is good and fine to define keyword-named functions and i think lispworks is being inconsiderate.
12:24:01
Xach
i think keyword-named functions should never appear in libraries or anything that is not a self-contained universe - so best used in your init files to define personal repl conveniences.
12:38:38
daphnis
i'm trying to load the source code for "Practical Common Lisp" in slime/sbcl, but am told "don't know how to REQUIRE ASERVE" ..
12:49:39
phoe
not the ASDF compile-file-error though, the actual error should be printed in the repl
12:52:10
Xach
to make it easier to find quicklisp dist-building errors, i've made some filtering that highlights only the fatal ERROR and WARNING parts from the build log.
12:52:42
Xach
i wonder if it would be useful to make that easily runnable by anyone so they can quickly get to the important output
13:10:31
drl
Why does (format t "~%~%~%~%~%~%~%~%~%~%~a~%~%~a: " "PRAYER Ver. 1.1 MAIN MENU" "<A>dd-records <E>dit-records <P>ray <R>eports <Enter>-exit") print both strings at the repl, but after using save-lisp-and die to make a stand-alone executable only the first string prints?
13:41:11
_death
interesting that FORMAT lacks a directive to clear/force/finish output.. in my OUT macro I added an (:fo [:wait boolean]) operator (no clear operator though.. never used it)
13:43:04
_death
I guess in FORMAT it would've been a "waste of a character" or something.. since it's not often you want to force/finish in the middle of output
14:21:19
ane
Xach: what sort of build tests are run for quicklisp distributions? how are cyclic dependencies or dependencies towards other QL packages handled for a single system?
14:25:52
phoe
ane: cyclic dependencies are detected on ASDF level, Quicklisp has nothing to do with that
15:09:49
Xach
ane: i build each system and record what it loads, and use that to build a static index of what to load
16:57:12
yk42bb
did you know that Common Lisp powers grammarly? vseloved worked on it with https://github.com/vseloved/cl-nlp
18:37:26
phoe
https://www.grammarly.com/blog/engineering/running-lisp-in-production/ is a famous blogpost by vseloved