Pike-devel January 2019

pike-devel@lists.lysator.liu.se

5 participants
14 discussions

Re: sortera filer
by Peter Bortas 14 Jan '19

14 Jan '19

On Mon, Jan 14, 2019 at 10:35 AM Mateusz Krawczuk <mkrawczuk(a)opera.com> wrote: > > Wouldn't it be better to go straight to Pike-devel to preserve the wisdom for broader audience? On the odd chance that pike-devel want late night musings in Swedish, then sure. I'm going to veto anyone else doing that though, so I don't think the chances of everyone agreeing to see my badly thought thru rants are high. Anyways, time to write something more coherent: We need a better API for handling directory listing, especially for coupling the listings with their metadata (stat struct). At the moment this is the most compact way of listing files in a dir sorted by creation time I could come up with: string mydir = "/tmp"; array files = get_dir(mydir); files = combine_path(mydir, files[*]); sort(files, file_stat(files[*])->ctime); And whenever automap feels like a good idea the API probably needs to be looked at. This will also explode in your face if files have been deleted between get_dir() and file_stat(). The question is what that API should be. We have a slightly extended API available in Filesystem: object fs = Filesystem.System("/tmp"); array files = fs->get_dir(); sort(files, fs->get_stats()->ctime); While this is cute if the directory contents is completely static (see Filesystem.Tar), not so much otherwise. I have some ideas of how a new API should look, basically: 1. Add a function (possibly to Filesystem) that returns both the listing and stats, so that TOCTOU error handling can be kept away from the user. 2. Add a convenience function where you can request a already sorted list based on any criteria you want. 3. bonus: more iterators Regards, -- Peter Bortas

1 0

Re: QuickType support
by Tobias S. Josefowitz ＠ Pike developers forum 11 Jan '19

11 Jan '19

>Those donât count ;) Well, yes, my point being these are why the return type even includes |object.

1 0

QuickType support
by Mateusz Krawczuk 09 Jan '19

09 Jan '19

Inspired by the debugger discussion, I've started implementing QuickType support for the Pike language. You can check it out by cloning my github fork[1], checking out to 'Pike' branch, and following the 'Contribute' section in README.md. After successful installation, you can run $ ./script/quicktype --lang pike test/inputs/json/samples/pokedex.json to see if it's working fine. The main motivation for this is generate Pike classes for the JSON-RPC messages specified in Microsoft's Debugger Adapter Protocol and Language Server Protocol. I imagine this could also turn out handy for people working with JSON-based APIs. There is plenty of work to be done here, like supporting enums and handling reserved statements, so I encourage you to contribute! Any feeback is more than appreciated. Mateusz [1] https://github.com/mkrawczuk/quicktype/tree/Pike

3 4

Process.run( ... ({ "stdin": "" }) ) fails
by ceder (-) Per Cederqvist ＠ Pike (-) developers forum 09 Jan '19

09 Jan '19

Process.run fails if stdin is an empty string. Here is a toy program that demonstrates it: -- cut here -- void run(string input) { werror("Input: %O\n", input); werror("Result: %O\n", Process.run( ({ "od", "-c" }), ([ "stdin": input ]) )); } int main() { run("foo"); run(""); return 0; } -- cut here -- The for invocation (which essentiall runs "echo foo | od -c") works fine. The second crashes with an error message: "Failed to convert argument to a source". This used to work in Pike 7.8, but fails in Pike 8.0.388 (in the version distributed with Debian 9 ("stretch")), and on the 8.0 and master branches in the Pike git repo. The complete output I'm seeing is: Input: "foo" Result: ([ /* 3 elements */ "exitcode": 0, "stderr": "", "stdout": "0000000 f o o\n" "0000003\n" ]) Input: "" Failed to convert argument to a source /usr/lib/pike8.0/modules/Shuffler.so:1: Shuffler.Shuffle()->add_source("") /usr/lib/pike8.0/modules/Process.pmod:617: Process.run(({"od","-c"}),mapping[1]) run-stdin.pike:4: /main()->run("") run-stdin.pike:11: /main()->main()

3 4

2026

2025

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