Pike-devel November 2016

pike-devel@lists.lysator.liu.se

9 participants
55 discussions

Pike 8.0.350 beta
by Peter Bortas 07 Nov '16

07 Nov '16

During this weekends Pike conference we resolved a few issues that prevented a new release, so here's a beta. Pike 8.0.350 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.350/Pike-v8.0.350.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.350/Pike-v8.0.350-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.350/Pike-v8.0.350-win32-oldli… Changes since Pike 8.0.276 (release 4) ---------------------------------------------------------------------- New features ------------ o Calendar Updated Calendar to use timezonedata from tzdata2016i. o Crypto.ECC Zero-pad short signature integers. o Protocols.HTTP.Server.HeaderParser It is now possible to enable non-normalization on the entire object, and not just on a per call basis. It is also possible to disable support for folded headers, as per IETFs latest specification. o CompilerEnvironment()->lock() This is a class that exposes the compiler internal lock. o Gz.deflate()->clone() This allows for testing compression. o gdb_backtraces() gdb_backtraces() is now available even --without-debug. o ADT.Heap()->low_pop() This function is analogous to low_peek(). o Protocols.WebSocket Parse query variables in WebSocket Requests. Bug fixes --------- o cpp Fixed stringify operator on strings containing escaped double quotes. o mkpackage Support $EXTRA_PLATFORM_TEST. o Threads.Condition Fixed double free at cleanup on exit. o Fixed multiple issues with cleanup on exit. o Whitefish Fixed wrong signedness. o Standards.EXIF Improved robustness of the EXIF parser. o Protocols.HTTP.Session Ignore malformed expiry dates in cookies. o Protocols.WebSocket Fixed handling of truncated frames. o _Roxen Backported multiple fixes from Pike 8.1. o Compiler Fixed broken range optimization. Removed optimization that considered the hostname() constant. Don't reference count direct cyclic references via mixed variables. o MasterObject Protect against the same file being compiled concurrently in multiple threads. Cast to program and cast to object should now be thread-safe. Survive RESOLV_DEBUG being enabled. o Stdio.FakeFile Improved sendfile compatibility. o Process.create_process Improved behavior under high signal pressure. o Sql.pgsql Improved robustness against stray destructs and exceptions. o Standards.BSON Fixed circular dependency. o Mappings Multiple optimizations in m_delete() and friends. Added flag MAPPING_FLAG_NO_SHRINK. o Calendar Updated timezone data to tzdata2016h. Building -------- o Nettle Since there are distributions that have removed nettle_secp_192r1 and nettlesecp_224r1 from the nettle library, these curved are now disabled by default. Enable them by compiling with --with-weak-curves. -- Peter Bortas

1 0

dynamic_dot: Warn when using . for indexing dynamically.
by Stephen R. van den Berg 07 Nov '16

07 Nov '16

Why would you warn for this? Or, to put it differently: why would it be better to avoid using the dot operator to index dynamically? -- Stephen.

2 1

Proposal: Checked subprocess calls
by Chris Angelico 06 Nov '16

06 Nov '16

Branch: rosuav/process-check-run Two features added to the Process module. Firstly, a simple wrapper Process.check_run that calls Process.run and throws an error if the exit code isn't 0; and secondly, a means for Process.run() to leave stderr attached to the console. The intention is for this to be used for subprocess invocations that should normally succeed, but which might fail under exceptional circumstances: https://github.com/Rosuav/shed/blob/master/double_compile.pike string build = Process.run(({"pike/bin/pike", argv[0], "-x", argv[1]}))->stdout; The intention is for this to run a process and return its stdout. I could, of course, manually check: mapping rc = Process.run(({"pike/bin/pike", argv[0], "-x", argv[1]})); if (rc->stderr != "") werror(rc->stderr); if (rc->exitcode) exit(1, "Oops\n"); But with this proposal, the code would look like this: string build = Process.check_run(({"pike/bin/pike", argv[0], "-x", argv[1]}), (["stderr": "-"]))->stdout; It's a fairly simple idiom (and it might be worth making check_run set stderr to "-" by default), and 99% of the time, it'll do the same as the equally-simple idiom that I currently use for any quick-and-dirty scripts - but if something goes wrong, check_run will make sure that you don't miss noticing it. There are, broadly speaking, two ways for a subprocess to signal that something went wrong: a message on stderr, or an exit code. They're handled independently (check_run looks for the exit code, and setting stderr to "-" lets the user notice an error message), so you can pick and choose. Is this something wanted in trunk? ChrisA

3 7

Commit policy in stable (8.0)
by Peter Bortas 05 Nov '16

05 Nov '16

During the Pike conference this weekend we decided to clarify the commit policy for the stable repository. So here it is written out: The stable branch is closed to new features unless approved by the release manager (Peter Bortas). Small bugfixes and any size documentation changes may be committed by anyone. Henrik Grubbström is exempt from this and may commit what he deems appropriate. Any feature change should come with an accompanying update to CHANGES, and the same for bug fixes where appropriate. This policy can also be found on https://pike.lysator.liu.se/development/git/policies/ Regards, -- Peter Bortas

1 0

pike-benchmark
by Arne Goedeke 05 Nov '16

05 Nov '16

Tobi and me have been working on a new suite of benchmarks for pike. The main reasons to use that instead of Tools.Shoot is to make it easier to compare different pike versions. It currently contains (modified) versions of all benchmarks from Tools.Shoot. They have been changed to better test what they were intended to test. Other things: * reduce the variance of test results and also diaplay their standard deviation to make comparisons possible * encourage people (also non pike developers) to add/send their benchmarks * make it easier to store benchmark runs and add tools to compare them In the long term it would be nice to integrate this and run it from xenofarm to automatically track performance during development. The repository name is 'pike-benchmark' and it is hosted on the same server as the pike git. everyone who has access to the pike git, can also access the 'pike-benchmark'. Feels free to add tests. Arne

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel November 2016