Pike-devel December 2019

pike-devel@lists.lysator.liu.se

5 participants
7 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

Remixml, javascript module
by Stephen R. van den Berg 25 Feb '20

25 Feb '20

This might be of interest to the Pike and/or Roxen community: https://www.npmjs.com/package/remixml I just launched it. Using it in a Single-Page-Application website. Any critical feedback is welcome (I'm currently the only user, so changes in the API are easy and still allowed). >From the description: Remixml is an XML/HTML macro language/template engine. The language and primitives used blend in completely with standard XML/HTML syntax and therefore integrate smoothly with existing XML/HTML syntax colouring editors. Requirements It runs inside any webbrowser environment (starting at IE11 and up). For historical reference: Remixml was originally inspired by RXML, the Roxen webserver macro language. -- Stephen.

1 1

Re: Image.PNG unable to find Gz
by Chris Angelico 31 Dec '19

31 Dec '19

On Wed, Jan 1, 2020 at 12:38 AM Tobias S. Josefowitz @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > >As of commit 1c31950, the Image.PNG module fails unless Gz has already > >been loaded. The PIKE_MODULE_IMPORT lines fail, and the module chooses > >to export nothing. > > > >Is there a way to force the Gz module to be loaded whenever Image.PNG > >gets loaded? > > Fixed on master by directly going for _Gz instead of Gz from > Image.PNG. Thank you! I was confused by the fact that the EXPORT lines seemed to match the IMPORT lines, but I guess they must have both been wrong. The fix works. ChrisA

1 0

Image.PNG unable to find Gz
by Chris Angelico 31 Dec '19

31 Dec '19

As of commit 1c31950, the Image.PNG module fails unless Gz has already been loaded. The PIKE_MODULE_IMPORT lines fail, and the module chooses to export nothing. rosuav@sikorsky:~/pike$ pike -e 'write("%d\n", sizeof(indices(Image.PNG)));' 0 But if the Gz module gets tagged first, it works: rosuav@sikorsky:~/pike$ pike -e 'Gz.crc32; write("%d\n", sizeof(indices(Image.PNG)));' 7 Is there a way to force the Gz module to be loaded whenever Image.PNG gets loaded? ChrisA

2 1

Immediate call_out takes 2ms
by Tomasz Jamroszczak 17 Dec '19

17 Dec '19

Hi. In Pike 7.8 calling call_out takes 0.002 ms. In Ubuntu's Pike v8.0 release 498 and in Opera's v8.0 release 610 it takes 2ms. Test program: int callouts_to_queue = 5; System.Time t = System.Time(); int before; void f() { exit(1, "this is not expected to run"); } void start() { before = t->usec_full; call_out(end, 0.0); } void end() { int delay = t->usec_full - before; werror("took %f ms\n", delay / 1000.0); exit(0); } int main() { for (int i = 0; i < callouts_to_queue; i++) call_out(f, 3.0); call_out(start, 0.0); return -1; } Is there a fix in younger version of Pike? Best Regards, Tomasz Jamroszczak

5 7

Crypto.MAC segmentation fault?
by Stephen R. van den Berg 03 Dec '19

03 Dec '19

FYI: $ pike Pike v8.1 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > object x = Crypto.MAC()->State("secretp"); Segmentation fault It might be abuse of the API (I was trying to find an incantation to create a secret to be used for JWT generation), but a segfault would not be allowed. -- Stephen.

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 December 2019