Hi !
Somebody raised this question on the yesterday chat.
So, CriTCL 0.32 works fine with AOLserver 4.0.
This is what I've done:
1. A checkout from CriTCL site:
% cd /usr/homes/zv/test
% cvs -d:pserver:[EMAIL PROTECTED]:/home/cvs co critcl
2. Log into the AOLserver's (4.0) ncp port and did:
% lappend auto_path /usr/homes/zv/test/critcl/lib/critcl
% ns_eval package require critcl
=> 0.32
3. Defined some example CriTCL procedure/command:
% critcl::cproc add {int x int y} int {return x + y;}
% add 123 456
=> 579
% ns_thread getid
=> 16
4. Logout from ncp port and log-in again (uses new thread!)
% add 123 456
=> 579
% ns_thread getid
=> 17
So. the on-the-fly compiled "add" command is now available
in all ncp, connection, detached, etc, threads.
I still did not examine the internals of CriTcl in terms
of MT-safety, but this can be left for somebody more
involved with the matter.
I've done my tests on a Solaris 2.6 with GCC. This should
also work on Linux.
Please note that CriTCL caches its *.so files in the
$env(HOME)/.critcl directory. It is the home dir of
the user owning the nsd process.
Cheers,
Zoran
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in
the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/