FIled a report. They say they've fixed it in the CVS tree (that was fast!). I feel like a good citizen .
Siggy
Search found 19 matches
- Fri Aug 06, 2010 1:50 pm
- Forum: Common Lisp
- Topic: Doc string & structs in clisp?
- Replies: 6
- Views: 6487
- Fri Aug 06, 2010 8:23 am
- Forum: Common Lisp
- Topic: Create hash key from pointer addresses
- Replies: 4
- Views: 5413
Re: Create hash key from pointer addresses
Okay, I think I'm going to use the equal designator. I'd tried it before and found that it doesn't descend into structs, but forgot to try it with lists (which is funny, 'cuz I was using lists at first). I think it'll actually be easier this way, since I don't want it to actually descend deep into m...
- Fri Aug 06, 2010 7:57 am
- Forum: Common Lisp
- Topic: Create hash key from pointer addresses
- Replies: 4
- Views: 5413
Re: Create hash key from pointer addresses
Ah, okay. Didn't know it had garbage collection, though that explains a lot.
I'll look into the designator and SXHASH. May be what I need.
Thanks for the pointers! Er. No pun intended. Honest!
Siggy
I'll look into the designator and SXHASH. May be what I need.
Thanks for the pointers! Er. No pun intended. Honest!
Siggy
- Fri Aug 06, 2010 3:56 am
- Forum: Common Lisp
- Topic: Create hash key from pointer addresses
- Replies: 4
- Views: 5413
Create hash key from pointer addresses
I'm rewriting an algorithm in CL that was originally designed in C. It involves running functions on the addresses of the children of binary tree nodes to generate hash keys. I've got control over the hashing function via Ingvar Mattson's generic hash table implementation. The problem now is how to ...
- Thu Aug 05, 2010 11:03 pm
- Forum: Common Lisp
- Topic: Doc string & structs in clisp?
- Replies: 6
- Views: 6487
Re: Doc string & structs in clisp?
The Hyperspec states that "an implementation is permitted to discard documentation strings at any time for implementation-defined reasons." I guess Clisp chooses to discard documentations to keep the memory consumption low, since using low memory is one of Clisp's main advantage. You're r...
- Thu Aug 05, 2010 1:08 pm
- Forum: Common Lisp
- Topic: Doc string & structs in clisp?
- Replies: 6
- Views: 6487
Re: Doc string & structs in clisp?
Er, yeah, the syntax I'm using is: (defstruct INF_node "A boolean expression in If-then-else Normal Form (INF).\ i.e. the nodes for our (R)OBDD." (var nil) ; The input variable this statement is for (integer from 1 to n) (low nil) ; Expression or terminal to follow if var's value is 0 (hig...
- Thu Aug 05, 2010 1:07 pm
- Forum: Common Lisp
- Topic: Doc string & structs in clisp?
- Replies: 6
- Views: 6487
Doc string & structs in clisp?
This isn't too big a deal -- but is it just me or is the documentation string functionality for structs broken in clisp? For example, in some of my code SBCL gives: * (documentation 'INF_node 'structure) "A boolean expression in If-then-else Normal Form (INF). i.e. the nodes for our (R)OBDD.&qu...
- Fri Jul 30, 2010 11:52 am
- Forum: Common Lisp
- Topic: Compiling to Binary in sbcl
- Replies: 2
- Views: 6859
Re: Compiling to Binary in sbcl
Thanks for the informative reply. What is going on is that UNIXoid systems require each terminating process to return an exit code . Gotcha. Right after I posted I wondered if that's what was going on -- but I ran off to lunch before having a chance to fix it. Solved now. Do note that cores saved by...
- Fri Jul 30, 2010 11:10 am
- Forum: Common Lisp
- Topic: Compiling to Binary in sbcl
- Replies: 2
- Views: 6859
Compiling to Binary in sbcl
Another newb question, this time in sbcl. Here's my "hello.lisp": (defun main() (print "hello, world!")) And here's what I run in sbcl: (load "hello.lisp") (sb-ext:save-lisp-and-die "my_binary" :executable t :toplevel 'main) And here's my result at the shell: ...
- Thu Jul 29, 2010 10:38 am
- Forum: Common Lisp
- Topic: Stack trace in clisp
- Replies: 2
- Views: 5199
Re: Stack trace in clisp
As for debugging, please see the Clisp documentation , in particular the section on REPL commands . Many thanks. I found the docs, but Google had taken me to how to do a straight-up trace, no a back trace, on the next page :-P. Oh yeah. You can type "help" and sometimes actually find some...