Subject: Re: Getting the PID in CLISP From: Erik Naggum <erik@naggum.no> Date: 23 Oct 2002 15:12:52 +0000 Newsgroups: comp.lang.lisp Message-ID: <3244374772669119@naggum.no> * Chris Beggy | I should have passed on the results rather than obscurly jumping | ahead to other results. That would have helped. | In my case: | | clisp prompt> (apropos "pid") | | returns nothing Absolutely fascinating. | My clisp version is: | | bash prompt%% clisp --version | | GNU CLISP 2.28 (released 2002-03-03) (built 3228004349) (memory 3228005268) | Features: (CLOS LOOP COMPILER CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) Mine does GNU CLISP 2.30 (released 2002-09-15) (built 3241717887) (memory 3244300085) Features: (ASDF MK-DEFSYSTEM COMMON-LISP-CONTROLLER CLX-MIT-R5 CLX-MIT-R4 XLIB CLX CLX-LITTLE-ENDIAN HAVE-WITH-STANDARD-IO-SYNTAX HAVE-CLCS HAVE-DECLAIM HAVE-PRINT-UNREADABLE-OBJECT CLOS LOOP COMPILER CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI UNICODE BASE-CHAR=CHARACTER SYSCALLS PC386 UNIX) Using `set-difference´ on these values, yours-mine yields (gettext) while mine-yours yields (asdf mk-defsystem common-lisp-controller clx-mit-r5 clx-mit-r4 xlib clx clx-little-endian have-with-standard-io-syntax have-clcs have-declaim have-print-unreadable-object syscalls) The crucial difference is `syscalls´. It appears to be a build option. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.