Pike-devel April 2019

pike-devel@lists.lysator.liu.se

5 participants
10 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: debugger, status and suggestions sought
by Mateusz Krawczuk 03 Nov '19

03 Nov '19

I think having both LSP <https://microsoft.github.io/language-server-protocol/> and DAP <https://microsoft.github.io/debug-adapter-protocol/> implementations for Pike would be awsome, but I feel that this discussion is getting further away from it's main point. We've been talking about LSP for a little during the Conference. There is a huge interest in it and I think we should move the LSP discussion to another mailing thread to avoid mixing contexts. Having a Pike debug adapter would also be great, but since DAP is used for estabilishing communication between IDE and the debugger, we can't move on with it until we actually have a debugger. >From what I understand the greatest challenge now would be to reach the local variables. I've heard that long time ago, the language got some optimizations that makes retrieving local variable names very challenging. Is it true? If yes, how we can jump this through? I would be more than happy to help crossing-out the remaining TO-DOs, if I only could get some itroduction and clues.

5 25

Delaying a future/promise by an arbitrary amount of time
by Stephen R. van den Berg 30 Apr '19

30 Apr '19

Say I'm holding a value, but I want to turn it into a promise that fulfills delayed by a predetermined amount of time, any suggestions as to where to put a utility function like that? The first thing that comes to mind would be to create a new member function of Concurrent.Future, i.e. next to the timeout() already there, we could introduce a delay() which would then semantically be something like: Return a Future that will be fulfilled with the result of this Future no sooner than after delay seconds. It's basically a sleep for promises. Any comments? -- Stephen.

2 20

Re: Operator assignment and strict_types
by Marc Simpson 24 Apr '19

24 Apr '19

Bumping this—I believe the behaviour is unchanged in HEAD. On Wed, Mar 28, 2018 at 5:30 PM Martin Nilsson (Coppermist) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Looks like a bug to me. I think these should all give the same > warnings. >

1 0

Re: Pike Meet-up 2019-Q2
by Mateusz Krawczuk 24 Apr '19

24 Apr '19

If moving the meeting to May 11th turns out to be impossible, would it be ok if I dropped by the Roxen office between 13th and 17th afternoon to ask some questions regarding the debugger? śr., 17 kwi 2019 o 11:53 Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> napisał(a): > 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 > six month mark from the latest conference is coming up soon, > it seems time to announce the second such meeting for 2019: > > Pike Meet-up 2019-Q2 > Date: 2018-05-04 (Sat) > Time: 10:00 - afternoon/evening > Place: Roxen IS AB > S:t Larsgatan 22A > Linköping > > Welcome! > > /grubba >

2 1

Re: Pike Meet-up 2019-Q2
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 24 Apr '19

24 Apr '19

>Any chance it might be moved to 11th May? Sure, I don't have any problem with either date. What do others say? >År., 17 kwi 2019 o 11:53 Henrik GrubbstrÃ¶m (Lysator) @ Pike (-) developers >forum <10353(a)lyskom.lysator.liu.se> napisaÅ(a): > >> 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 >> six month mark from the latest conference is coming up soon, >> it seems time to announce the second such meeting for 2019: >> >> Pike Meet-up 2019-Q2 >> Date: 2018-05-04 (Sat) >> Time: 10:00 - afternoon/evening >> Place: Roxen IS AB >> S:t Larsgatan 22A >> LinkÃ¶ping /grubba

2 1

Re: Interaction between automap and argument splicing segfaults
by Chris Angelico 04 Apr '19

04 Apr '19

On Thu, Apr 4, 2019 at 11:11 PM Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > > > The crash is on this line: > [...] > > If pike is built with PIKE_DEBUG, you get this fatal instead: > [...] > > So the crash is in the compiler proper, not in the execution of the > > program. > > Thanks for the report, test case and investigation. > > Fixed the code generator in Pike 8.0 and master. > Thanks! Confirming that it works with my original code too (from which the test case was derived). Much appreciated! ChrisA

1 0

Interaction between automap and argument splicing segfaults
by Chris Angelico 04 Apr '19

04 Apr '19

Test case: int score_image(string image, int r, int g, int b) {return 42;} array(int) getpixel() {return ({1, 2, 3});} int main(int argc, array(string) argv) { if (argc < 2) exit(0, "All good! Try again with -DBOOM for a segfault.\n"); array images = ({"foo", "bar", "quux"}); for (int x = 0; x < 10; ++x) //Without the loop, no boom { #ifdef BOOM array pixel = getpixel(); array(int) scores = score_image(images[*], @pixel); //Segfault #else [int r, int g, int b] = getpixel(); array(int) scores = score_image(images[*], r, g, b); //But avoiding @ works. #endif } } It's fine with either [*] or @pixel, and it's even fine with both, as long as it's not in a loop. But put all three together, and the interpreter segfaults before executing a single line of actual code, which I suspect means an issue at the compilation stage. (Can be triggered identically by casting "boom.pike" to program too.) Tested with the latest master branch, and with 8.0.735. No idea where to start looking for the cause, but it's a completely consistent crash. ChrisA

3 2

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 2019