Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (661 - 663 of 1030)

Ticket Resolution Summary Owner Reporter
#853 wontfix DEFVAR after DEFCONSTANT does not signal an error when no initial value provided Ron Garret
Description

SLSIA.

Welcome to Clozure Common Lisp Version 1.7-dev-r14715M-trunk  (DarwinX8664)!
? (defconstant x 1)
X
? (defvar x)  ; Should signal an error but doesn't
X
? (defvar x 1)
> Error: Can't redefine constant X .
#854 fixed Cannot pass command line arguments to CCL script Andrew Pennebaker
Description

I'm trying to rewrite a shebang in a CLISP script for CCL.

http://www.assembla.com/code/mcandre/subversion/nodes/common-lisp/problem.lisp

#!/bin/bash
#|
exec clisp -q -q $0 $0 ${1+"$@"}
exit
|#
#!/bin/bash
#|
exec ccl -Q -l $0 $0 ${1+"$@"}
exit
|#

But when I try to run my script, CCL interprets the script's arguments as CCL arguments.

$ ./problem.lisp --code "Hey" --jeer "Yo" ~/Downloads/problem.png
Unknown option: --code
usage: dx86cl64 <options>
	 or dx86cl64 <image-name>
	 where <options> are one or more of:
        -h, --help : this text
        -V, --version : print (LISP-IMPLEMENTATION-VERSION) and exit
        -K, --terminal-encoding : specify character encoding to use for *TERMINAL-IO*
        -n, --no-init : suppress loading of init file
        -e, --eval : evaluate <form> (may need to quote <form> in shell)
        -l, --load : load <file>
        -T, --set-lisp-heap-gc-threshold : set lisp-heap-gc-threshold to <n>
        -Q, --quiet : if --batch, also suppress printing of heralds, prompts
	-R, --heap-reserve <n>: reserve <n> (default: 549755813888)
		 bytes for heap expansion
	-S, --stack-size <n>: set  size of initial thread's control stack to <n>
	-Z, --thread-stack-size <n>: set default size of first (listener)  thread's stacks based on <n>
	-b, --batch: exit when EOF on *STANDARD-INPUT*
	--no-sigtrap : obscure option for running under GDB
	-I, --image-name <image-name>
	 and <image-name> defaults to dx86cl64.image
#855 fixed ARM port pc-lusering fails to recognize allocation sequence Gary Byers
Description

Running the simple test case from ticket:717 results in a trip to the kernel debugger with the complaint:

unexpected instruction preceding alloc trap.

The unexpected instruction is the (relatively new) branch around an unconditional uuo_alloc_trap. If pc_luser_xp() notes that a thread is at the alloc_trap, it expects the immediately preceding instruction to be a comparison, and that's now an instruction earlier.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.