Grubba fixed a string bug that looks pretty nasty for some special edge cases, so despite not being the first Tuesday of the month, here's a beta.
Pike 8.0.384 beta/release candidate:
https://pike.lysator.liu.se/pub/pike/beta/8.0.384/Pike-v8.0.384.tar.gz
Other builds:
https://pike.lysator.liu.se/pub/pike/beta/8.0.384/Pike-v8.0.384-Darwin-15.4.... https://pike.lysator.liu.se/pub/pike/beta/8.0.384/Pike-v8.0.384-win32-oldlib...
Changes since Pike 8.0.370 (release 6) ----------------------------------------------------------------------
Bug fixes ---------
o String character range
Fixed a bug where a string could incorrectly have it's character range start point set to 0 when added with an empty string. This in turn would incorrectly block the string from being used by functions that require strings without null characters as argument or incorrectly take optimization paths.
o VCDiff
Fixed type of decode_chunk().
o Parser.XML
UTF-8 encoded documents with initial BOM was not decoded correctly.
Serializing Parser.XML.Tree objects will now entity escape characters that can not be encoded in the selected output charset.
Regards,
Full freeze of the upcoming Debian stable release "stretch" is 5 February, and packages must have been uploaded at least 10 days before that to transition to testing in time, meaning that next month's Pike release will be the one in "stretch", so make it count! :-)
pike-devel@lists.lysator.liu.se