Pike-devel June 2018

pike-devel@lists.lysator.liu.se

2 participants
3 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

Sql.Sql()->query() returns double values with MySQL backend
by Tomasz Jamroszczak 11 Jun '18

11 Jun '18

When I run db->query("select columna,columnb from table") on SQLite, the query() code calls master_sql->query() and I get array of two-element mappings: ({ ([columna: valuea1, columnb: valueb1)], ([columna: valuea2, columnb: valueb2)], ([columna: valuea3, columnb: valueb3)] }). When I call the same Sql.Sql()->query() on MySQL, the query() code sees there's no master_sql->query() and it calls res_obj_to_array(master_sql->big_query()). This in turn returns array of four-element mappings: ({ ([columna: valuea1, table.columna: valuea1, columnb: valueb1, table.columnb: valueb1)], ([columna: valuea2, table.columna: valuea2, columnb: valueb2, table.columnb: valueb2)], ([columna: valuea3, table.columna: valuea3, columnb: valueb3, table.columnb: valueb3)] }). That's because of 19 year old https://github.com/pikelang/Pike/commit/1e1a5b4a89bad32c3be7d0554d7727b60e1… commit (the code is intact in Pike 8.1 version, although moved to https://github.com/pikelang/Pike/blob/8.1/lib/modules/__builtin.pmod/Sql.pm…). The same res_obj_to_array() is called for example in Sql.Sql()->list_tables(), but then the extra values are filtered out. That's quite unexpected to have double values when changing SQL backends. What's the rationale behind the commit? -- Best Regards Tomasz Jamroszczak

2 1

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