Marcin 'Qrczak' Kowalczyk wrote:
SISC (1.10.0-alpha) - main
#;> (import serial-io)
#;> (import threading)
#;> (define x (thread/new (lambda () (+ 2 2))))
#;> (call-with-serial-output-file "serialized" (lambda (ser) (serialize x ser)))
#;> (define y (call-with-serial-input-file "serialized" deserialize))
java.lang.InstantiationException: sisc.data.SchemeThread
[snip]
#;> (import networking)
#;> (define x (open-tcp-socket "localhost" 80))
#;> (call-with-serial-output-file "serialized" (lambda (ser) (serialize x ser)))
#;> (define y (call-with-serial-input-file "serialized" deserialize))
java.lang.InstantiationException: sisc.modules.io.SNetwork$SchemeTCPSocket
[snip]
What did you expect to happen instead? For the deserialization to spawn
a new thread and open a socket respectively? That's generally not
desirable or even possible (e.g. if the socket connection was inbound).
I suppose the error message could be friendlier, and be generated on
serialization, rather than deserialization.
BTW, documentation URL http://sisc.sourceforge.net/manual/html/ is broken.
That will be fixed soon. Meanwhile you can find the documentation for
the latest beta release at
http://sisc.sourceforge.net/manual-beta/
Matthias.
PS: I propose we move this discussion to the sisc-devel list (cc'ed).
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
| 
