On Tue, Feb 18, 2003 at 07:44:42PM -0500, Andrew Piskorski wrote: > On Tue, Feb 18, 2003 at 07:20:14PM -0500, Jim Davidson wrote: > > In a message dated 2/18/2003 5:53:54 PM Eastern Standard Time, > > [EMAIL PROTECTED] writes: > > > > - The BB_Nsv* C functions I've created in my nsvapi.c still aren't > > > working right in some cases, Tcl_GetCommandInfo is still claiming that > > > "nsv_set", etc. don't exist. This is despite the fact that the thread > > > calling these is now being spawned AFTER full server initialization.
Aha! I tracked that one down. Turned out it was just that in some cases, I was still passing in a null Tcl interp when I shouldn't have been. I fixed that, and now my app seems to be working fine in 4.0. Pending further testing anyway. :) Incidentally, if you have a null Tcl_interp * and so call Ns_TclAllocateInterp(NULL) in order to get a pointer to a real interp, that does NOT work in 4.0, as Ns_TclAllocateInterp just gives you NULL right back. In my case I don't actually need to do this, but if you don't know the virtual server name, what would be the proper way to get a Tcl interp, since Ns_TclAllocateInterp obviously no longer does it under 4.0? Or would this be the Wrong Thing To Do? -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com
