From: Kevin V. <ke...@vi...> - 2001-05-24 04:21:00
|
Just comitted a 'fix' to get sdcpp working under Borland C++ (apparently sdcpp calls alloca() with some big values, which causes a stack overflow, which causes all kinds of bad). 'Fixed' by #defining alloca as safe_calloc, just like on all the other platforms; this makes sdcpp one giant memory leak, just like on all the other platforms. But at least it doesn't take down Windows any more. With this out of the way, I propose cutting a release of 2.2.2. It's been along time since 2.2.1, and I don't know of any showstoppers. Anybody object? Peace, Kevin |