There is one other reason... to do things with the Tcl or AOLServer C level that can't be done in pure Tcl (that are specific to Tcl/AS, not the OS). There are a variety of things that can be done in C that just cannot be done in Tcl, as the API doesn't expose the information to do so.
Rob Seeger Zoran Vasiljevic wrote on 8/17/2004, 10:09 AM: > On Tuesday 17 August 2004 16:01, Nathan Folkman wrote: > > Off topic, but somewhat related... ;-) I know Tcl can't be used in all > > cases, and that sometimes you have to write C code to accomplish what's > > needed, but hopefully everyone can see the advantages of keeping as > much > > code as possible up at the Tcl level. > > > > I think we should continue to really look at the situations where folks > > are writing C code, and try to identify the reasons: > > > > 1. Performance related? The performance benefits of having to write the > > code in C out way the downsides of having to deal with things like > > memory allocation/freeing. > > > > 2. The Tcl API's don't exist which would allow you to do what you are > > trying to do. > > > > Mainly we write a C-level module for three reasons: > > 1. Performance > 2. Performance > 3. Performance > > Ok, there is a fourth reason of course: access to some OS-primitives > not handled by the Tcl abstraction layer (shared memory, third-party > db-libraries, just to name a few). -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
