[Chicken-users] types.db incorrect

[Jörg F . Wittenberger]

I found (and in this case have a fix to) one more fatal error in types.db.

thread-join! correctly return multiple values if the thread terminates
yielding multiple values.

However with the latest changes, I've seen several arity errors - and 
nothing did work anymore.

This little diff however fixed them (and the tcp-accept-timout issue from
my last message too):

$ diff -u ../chicken-core/types.db types.db
--- ../chicken-core/types.db    2011-09-04 19:56:37.000000000 +0200
+++ types.db    2011-09-05 19:55:59.000000000 +0200
@@ -2196,7 +2196,7 @@
(raise (procedure raise (*) noreturn))
(seconds->time (#(procedure #:clean #:enforce) seconds->time (number) 
(struct time)))
(terminated-thread-exception? (#(procedure #:pure) 
terminated-thread-exception? (*) boolean)) -(thread-join! (#(procedure 
#:clean #:enforce) thread-join! ((struct thread) #!optional * *) *)) 
+(thread-join! (#(procedure #:clean #:enforce) thread-join! ((struct 
thread) #!optional * *) . *))

(thread-name (#(procedure #:clean #:enforce) thread-name ((struct thread)) 
*)
             (((struct thread)) (##sys#slot #(1) '6)))
@@ -2463,7 +2463,7 @@
(tcp-abandon-port (#(procedure #:clean #:enforce) tcp-abandon-port (port) 
undefined))
(tcp-accept (#(procedure #:clean #:enforce) tcp-accept ((struct 
tcp-listener)) port port))
(tcp-accept-ready? (#(procedure #:clean #:enforce) tcp-accept-ready? 
((struct tcp-listener)) boolean)) -(tcp-accept-timeout (#(procedure #:clean 
#:enforce) tcp-accept-timeout (#!optional (or boolean number)) number)) 
+(tcp-accept-timeout (#(procedure #:clean #:enforce) tcp-accept-timeout 
(#!optional (or boolean number)) (or boolean number)))
(tcp-addresses (#(procedure #:clean #:enforce) tcp-addresses (port) string 
string))
(tcp-buffer-size (#(procedure #:clean #:enforce) tcp-buffer-size 
(#!optional fixnum) fixnum))
(tcp-close (#(procedure #:clean #:enforce) tcp-close ((struct 
tcp-listener)) undefined))

However I'm afraid - given the sheer amount of diff lines in types.db - that
this is not the only issue, is it?

If not, how would I turn the consequence - which is wrong code at this time 
- into a warning?

Thanks a lot

/Jerry
.........