> Interesting! I will have to check this. I believe it is
> there by mistake. That is, if you do not load xotcl package.
> Do you?
I do! But maybe the problem is elsewhere.
What I did here is: In the shared Tcl directory I have the aol-xotcl.tcl that
loads the XOTcl package (fine, as the
ns_log notice "XOTcl version $::xotcl::version$::xotcl::patchlevel loaded"
message appears in the serverlog).
I commented out the last three lines in that file:
#ns_eval {
# _my_sourcefiles [ns_library shared] [ns_library private]
#}
as I have my own "loader" in the private Tcl directory that loads .tcl
and .xotcl files in other, separate directories, as part of the startup.
As far as I can see, all the different .tcl and .xotcl files are sourced and
loaded.
With lazyloader=false, the error appears immediately
>[-main-] Error: invalid command name "::xotcl::unknown"
>invalid command name "::xotcl::unknown"
> while executing
>"namespace origin $pn"
> (procedure "_serializensp" line 12)
> invoked from within
>"_serializensp $n"
> (procedure "nstrace::statescript" line 36)
> invoked from within
>"nstrace::statescript"
> invoked from within
with lazyloader=true, as long as no XOTcl code is run, no error. So it might
in fact be some namespace related problem.
Bernd.
