#lisp - Tue 1 May 2007 between 20:54 and 23:03

NY Lost Funds



ignasthere is more content in the format string
the point is that i don't want to repeat the image-name parameter twice
rahulclhs ~*
specbothttp://www.lispworks.com/reference/HyperSpec/Body/22_cga.htm
ignasrahul: thanks
rahul: using goto in format instead of having named arguments seems like BASIC
rahulhehe
hrm
could we possibly have (mapcar 'foo ...) warn when FOO is not a defined function?
jsnellthat would probably be pretty easy, and could be done with one change for all standard functions that take function designators as arguments
ignashow to switch to some thread that is trying to show me the debugger in sbcl?
jsnellsb-thread:release-foreground
ignasjsnell: thank you very much
rahuljsnell: that would be a nice little patch :)
pingbakis there any planned ppc64 support for sbcl?
jsnellthe last time I heard anyone seriously contemplate doing that was probably over 2 years ago
pingbakok. kinda a large step to take to get sbcl up and running on a Cell.
thspingbak: Can't the Cell do ppc32 as well?
pingbakths: haven't tried it. there's a lot that Sony/Toshiba/IBM dumped off the chip to make the primary processor element smaller. Wouldn't be too surprised if some 32-bit instructions got dumped. Well, nothing like a good bootstrap compile to exercise the machine...
msinghis there a way to get more useful information out of slime running clisp: for example, when i type (car <tab> it will say (car arg0) which isnt too helpful
kpreidI hear clisp doesn't store that information.
msinghhmm. ok.
so um what do clisp users do when they want to know what arguments they should provide to say, reduce
sellout-mbC-c C-d h?
pkhuongbtw, while someone is hacking on PCL, you might find <http://discontinuity.info/~pkhuong/branch-summary.txt> (and .../branch.c for the corresponding source) interesting.
basically, by distributing unknown indirect call targets to different call sites, we can help branch prediction in some cases.
kencauseyAre there any Stefil users handy? I'm unclear about the work cycle still being somewhat new to CL. Let's say I flub some test code, I get an assertion failure, it gives me all sorts of options including retesting, but I don't see how I can really do anything but abort since I have to modify and reload the file to correct my error. What am I missing?
pisoI'm not a Stefil user, but possibly you could modify and reload the file and then select the retest restart?
kencauseyOK, what I guess I'm missing is how to reload the file without aborting first
open up a parallel repl?
kpreidthe debugger *is* a repl
usually
kencauseyaha, you see, I am missing something :)
pisoif you're in the repl, at the debugger prompt, just type (load "foo.lisp")
after modifying foo.lisp, of course
kpreidslime (if you're using it) makes this less true, though
kencauseythis is slime yes
actionpiso is not a slime user
pisois not a slime user
kencauseyI'm not clear where the prompt is, maybe it doesn't matter
kpreidthere should be an eval command

Page: 2 9 16 23 

IrcArchive

NY Lost Funds