Custom Query (1030 matches)

Given the new features for streams, namely the :sharing and :external-format improvements, it would be nice to be able to specify these keyword arguments for streams when doing something like:

(process-run-function "foo" #'foo :input :stream :output :stream)

I think having new keyword parameters like :input-args etc. would be better than adding a new keyword for each parameter (i.e. :input-sharing, :input-external-format, etc). Does this seem like a reasonable solution? (If so I can try to put a patch together to do this).

Alternatively, if a pipe stream creation API was exported (with support for these keyword options), then it would make it possible to create the pipe streams first, and simply pass them into process-run-function.

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.

The code for socket-error in l1-sockets.lisp passes several arguments to (make-condition 'socket-error ...) that the class apparently doesn't support, such as :situation.