2009-12-04 10:32:51, Pascal Georges: > Yes. And Tcl memory management is better than the libc one. Do you have link with more information?
> This is > why a Tcl maintainer (from Evolane company) suggested to me to switch > to Tcl API instead of classical malloc & new. See operator overloading > in C++ code (new & delete calls). Note that Tcl has an overhead of 8 > kB for each memory chunck but of course is smart enough at reusing > free parts of chuncks of memory. This is the overhead for C++-allocated memory or for Tcl-allocated memory? 8kb seems much too big for many small objects. > I only switched to Tcl API on Pocket > PC because on PC you usually don't care about a small exra amount of > RAM wasted. A small amount doesn't matter, I think only leaks matter - if those are fixed, everything should work smoothly. -- Michal Rudolf ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
