Zoran Vasiljevic wrote:
On Saturday 15 March 2003 18:45, you wrote:

Agree. I have skipped thru code and, apart from some
typecasts, I see no problems.

Hmmm ... I added a bunch of typecasts to avoid warnings at compile time, are you saying you had to add more or that you've taken some out? Most were to cast int to size_t - the code uses size information as a signed integer in some places (-1 as a flag) so simply changing the offending vars to size_t caused new warnings to pop up.

The warnings I was getting rid of had nothing to do with the
functionality I added, I just dislike our having code that generates
warnings and took the opportunity to clean it up while I was working on it.

I will import this in
SF on Monday, if it is ok for you.

Sure.


I might do this while I port other modules. It should be relatively
easy to do with srvPtr = NULL. Might turn out to be a trivial task.

I would probably take the approach of adding a new command to ns_cache, using servPtr == NULL as a flag seems a bit of a kludge. Most of the code works on a cache pointer with no other context information, implementing a true global cache will just involve adding a new proc to use a static tcl hashtable to map the name to a cache pointer. You initializing that hashtable and an associated static lock the first time the module is loaded, and only the first time ...


-- Don Baccus Portland, OR http://donb.photo.net, http://birdnotes.net, http://openacs.org



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/

Reply via email to