Changes since Pike 7.4.10: ---------------------------------------------------------------------- o Bugfix in Parser.C. "!=" is now considered one token instead of two. o Bugfixed loop over-optimization. o Postgres 7.3+ correctly detected. o "Backported funcion_object fixes from Pike 7.5"/"function_object() now behaves as in Pike 7.2. The other cases have been moved to function_program()."
o "MKREADSET: If elements e and e+1 have their places swapped, it
doesn't mean that there are overlapping ranges, just that the sort
function is unstable. It doesn't matter. Live with it."
o "Backported native argument handling fixes from 7.5." (java)
o Added System.dumpable() which can be used on Linux to enable coredumping even for seteuid/setegid processes. o Image.FreeType now selects the hopefully best character map when loading a font, instead of just picking a random one. o Fixed a bug that made searching for 8 bit strings in wider strings fail. o Fixed fencepost bug on overflow of the sprintf format info stack. o Fixed bugs in float parsing code, preventing very large positive or negative floats from being turned into 1.0 or -1.0.
method now always uses the old method while a new method, signal_autoconnect_new() uses the new interface. o Added missing GTK method set_style. o Fixed a compatibility problem with Getopt, which caused Pike 7.4 to behave slightly different from previous versions when running in posix-me-harder mode. o Fixed a bug in the code handling boundaries in multipart messages in the MIME module. o Multiline tokens are now handled better in Parser.Pike when running in streaming mode.
o Fixed a bug in sscanf when using % with wide characters.
o Fixed a bug in low_backtrace where the backtrace itself could be reported as an argument to the top function if it was of varargs type. o Fixed security hole with running next_object in a Pike with security. o Fixes to make dumping work in a fakeroot environment. o Line numbers for C programs are now shown in backtraces even without having to compile with rtldebug. o It is possible to turn on only gc debug with trace(1,"gc"). o The aim for 20% garbage between gc runs was calculated on the wrong total amount of objects, so in effect the gc aimed for 16.7% instead. o The decaying average calculation in the gc had a bug that caused the last reading (i.e. the last gc run) to be weighted very heavily. Thus a single "abnormal" gc run could cause the gc to schedule a fairly short or long gc interval the next time which might make it erratic. o More solutions to new and fresh autoconf compatibility problems, willfully introduced by the autoconf team. o Threads are disabled by default on OpenBSD/alpha <= 3.x.
o Java module now supports native method registration on alpha.
o Fixed floating point argument handling with native calls in Java module
o Pike will now look for the master path in SOFTWARE\Pike\ in the registry on Microsoft Windows. o Fixed icon transparency on Microsoft Windows. o Fixed a bug that could cause wrong line numbers in backtraces when ia32 machine code is used. o Fixed bug that could cause the stack to get out of synch when large 64 bit negative integers were converted to bignum objects. o Fixed bug in trampoline objects so that they can be indexed and printed as normal objects. o Accesses from child objects to symbols in their parent objects will no