Pike-devel April 2018

pike-devel@lists.lysator.liu.se

3 participants
5 discussions

Pike Meet-up 2018-Q1
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 20 Oct '21

20 Oct '21

Hi. At Pike Conference 2017 it was decided that we ought to hold a more informal meeting in Linköping ~ once every quarter. As the three month mark from the conference is coming up soon, it seems time to announce the first such meeting for 2018: Pike Meet-up 2018-Q1 Date: 2018-02-03 (Sat) Time: 10:00 - afternoon/evening Place: Roxen IS AB S:t Larsgatan 22A Linköping Welcome! /grubba

2 13

Operator assignment and strict_types
by Marc Simpson 07 Jul '20

07 Jul '20

Hi folks, It looks like operator assignment (op=), increment and decrement statements aren't subjected to the same typechecks as their more explicit equivalents. For example, neither the post-increment nor += statements below warn with strict_types enabled, even though they assign values outside of foo's restricted int domain: int(3..3) foo = 3; foo++; // no warning foo += 1; // no warning foo = foo + 1; // warning from strict_types Similarly, operator assignment on aggregates fails to elicit a warning: array(int) a = ({}); multiset(int) b = (<>); mapping(int:int) c = ([]); // no warnings a += ({ "hey" }); b += (< "hey" >); c += ([ "hey": "there" ]); // warnings from strict_types a = a + ({ "hey" }); b = b + (< "hey" >); c = c + ([ "hey": "there" ]); I'm guessing this is because the checks provided by the F_ASSIGN/F_ASSIGN_SELF case (las.c) only apply to direct assignment; op= and friends are presumably not instrumented for strict_types in the same manner. Have there been any discussions around addressing this inconsistency? Thanks, Marc

3 3

Pike 8.0.528 release candidate
by Peter Bortas 11 May '18

11 May '18

As is tradition a release has been prepared at the new years party with Champagne in one hand and keyboard in the other waiting for the clock to hit 24:00. Pike 8.0.528 release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.528/Pike-v8.0.528.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.528/Pike-v8.0.528-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.528/Pike-v8.0.528-win32-oldli… Real Mac build comes when Bill has time to have a look at that. Changes since Pike 8.0.498 (release 11) ---------------------------------------------------------------------- New Features ------------ o Sql.pgsql - Added support for PostgreSQL 10's stronger password authentication (SCRAM-SHA-256). - Slightly reduced overhead. - Support IEEE binary float database-wireformat. - Prevent new queries from starting in the local_backend. o Crypto.Hash.SCRAM New class to support SCRAM authentication. o Thread.ResourceCount New module to allow threadsafe race-condition-free counting of resources. o SSL.File Support query_fd() and set_buffer_mode() methods. o Toole.Standalone.check_http - Allow redirect responses. - Support --expect option. Bug fixes --------- o Compiler Improved variant robustness. o Calendar Updated tzdata to 2017c. o Crypto.CCM Fixed initialization of the iv. o Filesystem.Monitor - Fixed issue with next_poll being set to zero causing polling every second. - Fixed indexing the NULL value error when InotifyMonitor was used in combination with a filter_file() that doesn't accept everything. o HTTPLoop: Fixed some potential race conditions. o Image.Image - Improved argument checking in apply_curve(). Non-integer array values lead to use of uninitialized curve values. o Image.PVR Fixed size check for twiddled images. o MIME Support trailing newline in MIME part epilogues. o Protocols.HTTP Fixed incoming chunked transfers (timed async works now, chunk options are properly 'parsed'). o Protocols.LDAP Fixed race condition on initializing LDAPS. o Search.Utils Updated debug string format. o Sql.pgsql - Suppress spurious 'File not open' blurts on stderr when the connection is still pending and we inspect the connection object. - Signal EOF early before closing the SQL result portal and thoroughly cleanup bufcon/stashcount to prevent occasional deadlocks on asynchronous object destructions. - Suppress rare "access in destructed object" messages. - Rip out fundamentally flawed reconnect logic, made failures consistent. - Repair SSL connect logic. - Update documentation. - Repair fetch_row_array(). o mktime/System.TM Make timezone management consistent (especially UTC handling). o Standards.IIM Disabled debug output for unknown segment markers. o Stdio.send_file Improved support for TLS/SSL; wait for TLS handshake to complete before calling the sendfile done callback when sending an empty string. This fixes the issue where the connection got closed before TLS handshaking was completed, confusing the other side. o Image Creating images with mode "grey" now works as documented, e.g. Image.Image(10,10,"grey",123); Optimizations ------------- o mktime/System.TM Considerable speedup and a reduction in codesize. Building & Tools ---------------- o Image.SVG Fall back to using the unprefixed pkg-config if the arch-prefixed doesn't exist. o Mysql Support MariaDB 10.2 headerfiles. o precompile Support precompilation with Pike 8.1 again. o smartlink Fixed multiple issues on Darwin & NetBSD. o Whitefish Use the standard VPATH. o Yp Support using libtirpc. Glibc 2.26 has removed the Sun RPC implementation... Regards, -- Peter Bortas

5 12

No mercy!
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 17 Apr '18

17 Apr '18

Annoying Hilfe bug: Pike v8.0 release 498 running Hilfe v3.5 (Incremental Pike Frontend) > string a = #" >> shoot to kill"; > string b = #" >> set phasers to stun"; No setting named "phasers" exists. >>

2 2

Into and such
by Lance Dillon 08 Apr '18

08 Apr '18

Just out of curiosity, how does intp() and such work. Say you have int|float x, then x=5.0. Does intp test the type of the variable, or the type of the contents. Does intp(x) return true because x is of type int (also of type float), or false because the contents of x (currently 5.0) is float, so not an int at that point. I'm thinking contents, not variable itself, so you can do checks against it. Sent from Yahoo Mail on Android

3 4

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 April 2018