As mentioned in Tcl Bug 2557696, I believe the memory allocation
routines enabled when Tcl sources are built with the USE_TCLALLOC
directive have some problems.  I think there are 64-bit issues and
argument overflow checking issues.  I've been correcting such things
in other allocators that I know get used.

I'd rather not waste time fixing the USE_TCLALLOC allocators if it
no longer has any users.  I'd rather just purge the dead code.  I
would do this only on the HEAD sources.

So here's the call.  Is anyone making any use of a USE_TCLALLOC build
of Tcl?  Can anyone report successful test or use of it for any
productive purpose in the last year or two?

-- 
| Don Porter          Mathematical and Computational Sciences Division |
| donald.porter@[...].gov             Information Technology Laboratory |
| http://math.nist.gov/~DPorter/                                  NIST |
|______________________________________________________________________|

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Tcl-Core mailing list
Tcl-Core@[...].net
https://lists.sourceforge.net/lists/listinfo/tcl-core