on win32 os:priority does not accept parameter pid as I expected it to do
after reading the clisp impnotes:
> (os:priority (os:process-id))
*** - Win32 error 6 (ERROR_INVALID_HANDLE): The handle is invalid.
background: I try to make SciTE and CLISP "play nicely together", without building
any of these. In order to remote-control CLISP I am using an ext:make-buffered-input-stream,
which works fine so far. However, I'd like Lisp to "idle" while it waits for input,
to save energy, carbon-dioxide and laptop-battery.
A delay, pause, or wait function would also be fine, however after days of studying the impnotes
I did not find any suitable but the os:priority…
I used the ordinary latest win32 download, here is the -version:
GNU CLISP 2.49 (2010-07-07) (built on STSst063.jenty.by )
Software: GNU-C 3.4.5 (mingw-vista special r3)
gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -D_WIN32 -DENABLE_UNICODE -I/usr/local/include -DDYNAMIC_FFI -I. -L/usr/local/lib -lintl /usr/local/lib/libreadline.dll.a -L/usr/local/lib -ltermcap /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a -luser32 -lws2_32 -lole32 -loleaut32 -luuid -liconv -L/usr/local/lib -lsigsegv libgnu_cl.a
SAFETY=0 HEAPCODES STANDARD_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
(READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS
LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 WIN32)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: C:\Programme\clisp-2.49\
User language: ENGLISH
Machine: PC/386 (PC/686) H5R7E2RCRR03WJW
thanks for your bug report.
I just fixed it in the hg.
please build from the sources and check if the bug is indeed fixed.
thanks for the fast fix
unfortunately I am a true lisper and promised myself never to touch C.
building… what's that? Do I have to…. ehm, well, when will there be the
next release of a built CLISP? Meanwhile there is enough work to
program the interface between SciTE and CLISP.
you will need to ask a volunteer on clisp-list to build clisp for you on windows.