Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (379 - 381 of 1030)

Ticket Resolution Summary Owner Reporter
#842 wontfix don't require quotes for toplevel 'cd' command Brandon J. Van Every
Description

I suggest that quotes should not be required when typing the directory name for the toplevel 'cd' command.

I am evaluating Clozure CL on x86 Windows. My 1st experience of it was trying to change my working directory so that I could load a lisp file. I typed :? and got some help. PWD worked as per the help given. CD DIR seemingly did not. Whatever I typed, I got errors. Didn't matter if it was cd C:/blah, :cd C:/blah, or :cd \blah. I started to think that the Clozure port on Windows might not be very reliable, since I had read it was relatively recent.

I pulled the latest Clozure version from SVN just in case this was a bug that had been fixed. I searched the bug tracker for entries. Only then did I notice that all examples were given as cd "X:/some/dirname" with quotes around the directory name. This is counter to typical command shell usage. I did figure out the necessity of the colon : escape mechanism; I don't begrudge that. But if I'm going to type a colon : escape, why should I have to type any more extra mumbo jumbo to get the command to behave like a shell command?

If it is not feasible to remove the quoting requirement, the :? HELP should at least say CD "DIR" and give an example, so that a new user knows that they have to type quotes around the directory name.

#841 invalid Better error stack traces Andrew Pennebaker
Description

Somewhere in my code is a bug, but it's hard to track down.

? (gen-game)
> Error: value . is not of the expected type LIST.
> While executing: (:INTERNAL (PRINT-OBJECT (CL-ROGUE:LEVEL T))), in process listener(1).

Only by trial and error can I find out which function call is to blame.

Please list the calling functions in an error trace, not just "process listener".

#840 fixed Lisp non-conformance created by load Martin Brooks
Description

Start a fresh CCL 1.6 (64bit Mac OS 10.6.7) and eval the following two forms; this will work as it should.

(defstruct foo a)

(defun baz () (flet ((foo-a (x y) (+ x y))) (foo-a 1 2)))

Now put the two forms in a file, and load the file. The result is a compiler error:

? (load "Users/brooks/Desktop/test.lisp")

Error: While compiling BAZ :

Extra args (1 2) for (LAMBDA (FOO) ...), in process Listener(6).

Alternatively, if the flet defined foo-a to have a single arg, then the compiler would not complain, but subsequently eval'ing (baz) will generate a type error:

? (baz)

Error: value 2 is not of the expected type FOO.

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