Pike-devel April 2020

pike-devel@lists.lysator.liu.se

4 participants
8 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

Crypto.Password and Blowfish
by Stephen R. van den Berg 19 Jul '20

19 Jul '20

Has anyone attempted to add support for Blowfish encryption to Crypto.Password? I have some $2y$... prefixed passwords (interfacing with the PHP password_verify()) which I need to verify. -- Stephen.

4 11

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

RFC: Attributes in Markdown text
by Chris Angelico 21 May '20

21 May '20

See branch: rosuav/markdown-attribute-syntax There's a not-very-well-known syntax supported by some Markdown parsers (including GitHub Flavored Markdown) that allows HTML attributes to be attached to a paragraph of text: Text goes here blah blah blah {: someattr=value otherattr=otherval} This is extremely handy for making small adjustments to the display of something, particularly with shorthands for class and ID, for use in CSS: {: .someclass} {: #someid} However, it's not well documented and I can't find a standard anywhere for it. It is something that I personally would find extremely useful, and am currently implementing by subclassing the Markdown module and tweaking the parser. Would anyone else find this of value? Conversely, would anyone find that this causes issues? ChrisA

3 4

Build failure on macOS (HEAD of master)
by Marc Simpson 01 May '20

01 May '20

Hi all, FYI, it looks like master no longer builds on macOS due to the MTU additions in [44f12ac]: .../src/modules/_Stdio/file.c:5526:16: error: use of undeclared identifier 'IP_MTU' int option = IP_MTU; .../src/modules/_Stdio/file.c:5541:14: error: use of undeclared identifier 'IPV6_MTU' option = IPV6_MTU; Best, Marc

1 1

SQLite query segfaults
by Marc Simpson 30 Apr '20

30 Apr '20

Hi folks, It seems that I can reliably segfault recent Pike 8.1 installs when using sprintf-style SQLite queries: $ echo ' create table demo(a, b); insert into demo(a, b) values(1, "abc")' | sqlite3 demo.db $ pike Pike v8.1 release 13 running Hilfe v3.5 [...] > Sql.Sql db = Sql.Sql("sqlite://demo.db"); > db->query("select * from demo"); (1) Result: ({ /* 1 element */ ([ /* 2 elements */ "a": "1", "b": "abc" ]) }) > db->query("select * from demo where a = :a", ([":a": 1 ])); (2) Result: ({ /* 1 element */ ([ /* 2 elements */ "a": "1", "b": "abc" ]) }) > db->query("select * from demo where a = %d", 1); Segmentation fault This occurs on both macOS and Linux; on macOS, segfaults are observed when the SQLite module is linked against either MacPorts' SQLite 3 or the system wide dylib in /usr/lib. Note that query() with a mapping argument doesn't segfault; furthermore, no such segfault occurs under Pike v8.0 release 702. Please let me know whether this is reproducible (and/or whether more information is required). Thanks, Marc

3 4

Interest in zip archive resolver?
by H William Welliver 29 Apr '20

29 Apr '20

Hello all, I’ve been going through some of my long ignored feature branches and found a few that might have promising code. Is there any interest in being able to specify (include/program/module) paths in terms of zip archives? At one point I wanted to be able to provide an entire application as a single file, and wrote support for various paths inside of zip files. The code I wrote is about 7 years old, but it was/is used and I’d be happy to fix it up if no one has major objections. The code in question provides support for including zip files as part of paths for -I, -P and -M: pike -M /path/to/some.zip or pike -M /path/to/some.zip/folder As well as the idea of a properly formatted archive with well know directories for modules, includes and programs: pike -A /path/to/some.zip where some.zip looks like: include/* modules/* And implicitly sets -I, -M and -P to include/, modules and / respectively. Any thoughts, opinions, suggestions? Bill

3 2

Re: Interest in zip archive resolver?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 17 Apr '20

17 Apr '20

>I hadn.FN"t really thought of making it executable$B!D(B I think thereN"s a >magic cookie at the beginning of a ZIP file so a hashbang might not >work if the archive were intended to be spec-compliant. No, the magic cookie (PK\005\006) is at the _end_. The central directory and file entries also have magic cookies (PK\001\002 and PK\003\004 respectively), but those don't have to be at any specific position but are pointed out as file offsets rooted in the PK\005\006 header at offset file_size-22. AFAICR it was standard practice to make self-extracting ZIP:s on MS-DOS by just cramming an MZ binary before the archive (and adjusting the offsets accordingly). It should be pretty easy to just put something at the start if creating the archive by hand like Filesystem.Zip is doing.

1 0

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 2020