Pike-devel November 2016

pike-devel@lists.lysator.liu.se

9 participants
52 discussions

BSON codings and multisets
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 22 Nov '16

22 Nov '16

I have done some work to connect to MongoDB using Pike and that requires the use of BSON. Unfortunately, MongoDB seems to think that BSON is an ordered document, i.e. the order of the indices in the encoded document matters. This is something that Pike doesn't support as we use mappings as input (which does not have a guaranteed order). I see two ways out of this; either we extend the BSON API in pike to allow for a sorted array to specify the indices in the order they should be added to the BSON document or we fix the multiset implementation so that it becomes more like what mast intended it to be and switch to that. (His intention was to make it more like an ordered mapping) Out of the two, option 1 is trivial and that is what I did for now. It is ugly as **** though and I'd much prefer option 2 but that seems to be a lot more complicated if you ask me. In the long run, I guess we should ask ourselves what the purpose of the current multiset implementation is. I can't really see any value in having the current implementation tbh, but I might be missing something. So, what do people think? Should we create an extended BSON API as a short (or maybe long-term) solution to get ordered BSON documents and what are the opinions on multisets?

1 0

Optimization
by Jonas Walld�n ＠ Pike developers forum 22 Nov '16

22 Nov '16

Just thinking of Nilsson's trick here: - if(has_value(str, "\0")) + if( String.range(str)[0]==0 ) I was about to suggest moving this optimization to f_has_value(), but I now see that it's already part of f_search() (called by f_has_value) for string/string cases so this is just an obfuscation.

1 0

Pike 8.0.294 beta
by Peter Bortas 22 Nov '16

22 Nov '16

Pike 8.0.294 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.294/Pike-v8.0.294.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.294/Pike-v8.0.294-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.294/Pike-v8.0.294-win32-oldli… -- Peter Bortas, NSC

2 1

CHANGES for next release
by Peter Bortas ＠ Pike developers forum 22 Nov '16

22 Nov '16

The entries added to CHANGES since 8.0.276 looks a bit sparse when compared to the actual commits. Should any of this get an entry?: http://pike-librarian.lysator.liu.se/index.xml?m=pike.git&starttag=&start=J…

1 0

Pike 8.0 release 5 (8.0.358)
by Peter Bortas 20 Nov '16

20 Nov '16

Pike 8.0 rel 5 is now out. This release is dedicated to Per Hedbor, who we sadly lost at the end of the summer. He was a programming genius, a large contributor to many parts of Pike, and probably the most prolific producer of Pike application code in the world. But above all we will remember him as a great friend. Source: https://pike.lysator.liu.se/pub/pike/all/8.0.358/Pike-v8.0.358.tar.gz Binary builds: https://pike.lysator.liu.se/pub/pike/all/8.0.358/Pike-v8.0.358-Darwin-15.4.… https://pike.lysator.liu.se/pub/pike/all/8.0.358/Pike-v8.0.358-win32-oldlib… 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. The 8.0.358 build is almost equivalent to the 8.0.352 release candidate. The difference is fixes the the testsuite to fix some broken tests. For exact details, see http://pike-librarian.lysator.liu.se/index.xml?m=pike.git&starttag=&start=8… Regards, -- Peter Bortas

1 0

Promises in Pike vs other languages
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 09 Nov '16

09 Nov '16

I have spent some time looking at the new stuff in Concurrent.pmod that Grubba has added to 8.1. Mostly it is code relating to the concept of Promises and Futures which are very popular amongst JavaScript people these days. I have noted that there seems to be some rather striking differences between how JavaScript treats promises and how Pike does it. I'm not sure this is a good thing(tm) and therefore I'd like to bring this up before 8.1 stabilizes. In Pike, we have two methods that register callback functions, Future.on_success() and Future.on_failure() as opposed to JS where only one method, then(), is used to register both callbacks. I don't mind having two different methods, but for easier transition between the two languages (i.e. for people writing both client-side and server-side code) having the same API would probably help. A bigger problem imho is the difference in how promises are actually resolved. In JavaScript, the return value of then() is always a *new* promise which then allows for chaining. In Pike, we return the same promise object. This means that code like my_promise->on_success(foo)->on_success(bar) in Pike would result only in a call to bar() once my_promise is resolved whereas in JavaScript, foo() would be called and it's return value would be the input to bar in a new promise. The whole creation of promises is also somewhat awkward in Pike. In JS, you simply pass a callback that will do all the work and that will recieve a success callback and a failure callback as arguments and off you go. In Pike, I'm not sure what the best way to do it is. I really like the idea of having promises in Pike, but would it not be much better if we tried to implement an API more similar to what the JS folks are used to? At least I think so... Here are three links to good resources I've found regarding promises in JS. I'm sure there are a ton of others as well. https://promisesaplus.com/ http://www.mattgreer.org/articles/promises-in-wicked-detail/ http://bluebirdjs.com/docs/api-reference.html

4 10

lyskom <-> pike-devel mailinglist gateway still broken
by Stephen R. van den Berg 09 Nov '16

09 Nov '16

Oh, and for the record: I'm suspecting the lyskom <-> pike-devel mailinglist gateway is still broken. Why does it break so often? -- Stephen.

2 1

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

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