freenode/#lisp - IRC Chatlog
Search
17:12:11
fiddlerwoaroof
jmercouris: minion doesn't seem to have remembered, but it's possible to have dyld on a mac automatically find a library relative to your application's bundle
17:13:20
fiddlerwoaroof
I've recently been experimenting with configuring ASDF to dump all its compilation results into my application bundle, so I can use this to find annoying things like osicat.dylib
18:12:31
kapitanfind-us
Question I have: say I have a system and I run sbcl and want to load a system from my local my-package.asd
18:14:53
mfiano2
It has to be located in a path asdf looks for, unless you call asdf:load-asd before asdf:load-system
18:16:01
mfiano2
IIRC it also needs to have a filename the same as the system name, sans file extension
18:19:36
mfiano2
`sly` on the asd file? That just starts up an image and sets the current working path to that of the file. sly doesn't load an asd
18:20:41
mfiano2
By the way, it is common practice to use Quicklisp rather than asdf directly in most situations
18:23:05
kapitanfind-us
fiddlerwoaroof: so do I understand right, you "compile" first then use a package manager to load it back in memory
18:25:26
kapitanfind-us
ok so my next question would be, is there a way to set this up every time I launch sbcl (via sly)
18:26:01
fiddlerwoaroof
There's probably a hook you can setup, but I don't really find this worth automating
20:58:25
no-defun-allowed
Are there any libraries or any code for writing out a ratio as a decimal number?
21:02:58
no-defun-allowed
(Looking at that stupid pidigits benchmark) I have a lot more precision than what a float can provide.
21:04:06
Shinmera
When printing a ratio with ~f your implementation may or may not use a more precise method to print it
22:21:53
pfdietz
Specifically, it would get into a mode where it ignored interrupts. If I then caused an error, it would throw an interrupt condition instead of the intended error.
0:42:23
phoe
Implementors of #lisp: do we have anyone proficient with debugging ANSI LOOP? I am trying to fix ANSI-TEST failures on CCL.
0:42:48
phoe
One of them is the infamous (loop for x of-type (integer 1 5) from 1 to 5 collect x) that fails on safe code because (setq x 6) is happening behind the scenes.
0:48:12
White_Flame
"the loop terminates when the variable var passes the value of form2" Sounds like the bug is with the test. The actual variable is supposed to breach past the "to" value
0:51:21
White_Flame
hmm, no I think I might be wrong. That's from downto/upto. "to" specifically flags an ending value, not a threshold
1:04:24
phoe
I asked specifically about ANSI LOOP because this implementation of LOOP is what is used inside CCL.
1:10:43
phoe
pjb: dead code per se isn't invalid, it just won't be reached and a sufficiently smart compiler will optimize it away
1:15:55
White_Flame
I still think the test itself is badly written. Its declaration mislabes what ranges it asks LOOP to calculate for X
1:16:25
White_Flame
from CLHS: (let ((x 1)) (loop for i from x by (incf x) to 10 collect i)) => (1 3 5 7 9)
1:17:16
pjb
The value 6 is not of the expected type (integer 1 5). on "Version 1.12-dev (v1.12-dev.4-4-gd9740256) Darwinx8664"
1:18:21
White_Flame
in http://www.lispworks.com/documentation/HyperSpec/Body/06_abaa.htm is "stepped[1]" supposed to refer to the glossary with that [1]?
1:18:42
phoe
I ask because ECL also uses a modified ANSI LOOP and maybe it has fixed this issue already.
1:19:10
White_Flame
"step v.t., n. 1. v.t. (an iteration variable) to assign the variable a new value at the end of an iteration, in preparation for a new iteration."