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.0-x86_64-macports
    
https://pike.lysator.liu.se/pub/pike/beta/8.0.384/Pike-v8.0.384-win32-oldlibs.msi


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,
-- 
Peter Bortas
  • Chri... Peter Bortas
    • ... Magnus Holmgren, Millnet/Lysator/Debian/Mensa @ Pike developers forum

Reply via email to