Custom Query (1030 matches)

From: Scott McKay <>

> From: Len Livshin <>
> Date: March 26, 2008 9:22:10 AM EDT
> 
> $ /usr/local/openmcl/working-0711-8771/lx86cl64
> Welcome to Clozure Common Lisp Version 1.2-r8771MS  (LinuxX8664)!
> ? (parse-integer nil :junk-allowed t)
> NIL
> 0
> ?
> 
> I think that the common sense interpretation of ":junk-allowed" parameter is that you're allowed to pass junk *in* a string,
> not that you're allowed to pass junk *instead* of a string...

What Dan says.  'parse-integer' takes a string argument;
:junk-allowed t should not change its type signature.

To load the system call interfaces, one currently has to copy this piece of code:

(eval-when (:compile-toplevel :execute)
  #+linuxppc-target
  (require "PPC-LINUX-SYSCALLS")
  #+linuxx8664-target
  (require "X8664-LINUX-SYSCALLS")
  #+darwinppc-target
  (require "DARWINPPC-SYSCALLS")
  #+darwinx8664-target
  (require "DARWINX8664-SYSCALLS")
  #+freebsdx8664-target
  (require "X8664-FREEBSD-SYSCALLS")
  )

This is rather inconvenient for the user, as every new architecture and every new operating system requires manual patching of the application that uses the system calls. The upcoming 32 bit X86 port will make this particularily apparent.

I would suggest that CCL provided a single "SYSCALLS" module that selectes the right module to load, so that the application can use

(require "SYSCALLS")

If the eval-when could go, it'd be even better.

I am aware that the system call interfaces vary between architectures and operating systems and that one cannot expect (require "SYSCALLS") to provide for one common interface to the system. Given that most operating systems supported will be Unix based, there is significant overlap between the variants and thus it _will_ be possible to just use code cross-platform in many cases.

This is easily reproducible. In any editor or listener, do a m-x grep, which asks for a pattern in the mini-buffer. Now do a command-v to paste, and it crashes into the kernel debugger.