Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

ADT.OrderedMapping() and duplicate entries
by Stephen R. van den Berg 07 Mar '20

07 Mar '20

Can it be considered a bug that when you add a duplicate key to an ADT.OrderedMapping() that it does add the key/value at the end, but fails to delete the already present same old key (value)? Shall I fix it? -- Stephen.

1 0

Issue tracker
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 06 Mar '20

06 Mar '20

Hi. At the 2020-Q1 meet-up we decided to use the GitLab issue tracker at https://git.lysator.liu.se/pikelang/pike/ for Pike. Issue numbers were reserved as follows: * 1 - 7999 Bugzilla bugs ([Bug XXXX]). * 8000 - 9999 YouTrack issues ([PIKE-XXXX]). * 10000 - New (GitLab) issues (#XXXXX). The historic bugs from http://bugzilla.roxen.com/ have now been imported (with the same tracking numbers). This means that they (well most of them) are publically available again. Note that due to the GitLab API used for the import, all issues and comments are attributed to Peter Bortas, although the first line of each mentions the original commenter. /grubba

1 1

Debugger status
by H William Welliver 27 Feb '20

27 Feb '20

Hi all- I anticipate having some free time coming up and thought I might spend some of that working on the debugger project. However, I’m not really sure where things stand. So, here are some questions to help me understand the situation: 1. How much of the code in play is related to what I originally had in the debugger concept branch? 2. Has any of that been merged into another working location? 3. I seem to recall there being a review of (some) debugging code. Has action been taken on any of those suggestions? 4. Mateusz had been working on an implementation of the debug server protocol. Is that complete from a client server standpoint? 5.I think at one point there was a demo project but that it didn’t actually connect to pike. What exactly is the status of that, or of the inevitable javascript-based plugin for VS Code? 6. Anything else I’m missing? Or put another way: I want to write a pike program in, say, VS Code, and I want to be able to debug it there. How far from that goal will I be, and what needs to be done to get there? Thanks in advance! Bill

3 2

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: Pike-devel Digest, Vol 173, Issue 3
by David Tapia 23 Jan '20

23 Jan '20

Hi all, Process.spawn has a vulnerability: Process spawn(string command, void|Stdio.Stream stdin, void|Stdio.Stream stdout, void|Stdio.Stream stderr, // These aren't used. Seems to be part of something unfinished. /mast //function|void cleanup, mixed ... args ) //! Spawns a process that executes @[command] as a command shell //! statement ("@expr{/bin/sh -c @[command]@}" for Unix, "@expr{cmd /c //! @[command]@}" for Windows). //! //! @param stdin //! @param stdout //! @param stderr //! Stream objects to use as standard input, standard output and //! standard error, respectively, for the created process. The //! corresponding streams for this process are used for those that //! are left out. //! //! @returns //! Returns a @[Process.Process] object for the created process. //! //! @seealso //! @[system], @[popen] { mapping(string:mixed) data=(["env":getenv()]); if(stdin) data->stdin=stdin; if(stdout) data->stdout=stdout; if(stderr) data->stderr=stderr; #if defined(__NT__) // if the command string command is not quoted, add double quotes to // make sure it is not modified by create_process if (sizeof(command) <= 1 || command[0] != '\"' || command[sizeof(command)-1] != '\"') command = "\"" + command + "\""; return Process(({ "cmd", "/c", command }),data); #elif defined(__amigaos__) return Process(split_quoted_string(command),data); #else /* !__NT__||__amigaos__ */ // return Process(({ "/bin/sh", "-c", /*command*/ }),data); // Fix ? *return Process(({ "/bin/sh", "-c" }) + split_quoted_string(command),data);* ** #endif /* __NT__||__amigaos__ */ } Regards El 23/1/20 a les 12:00, pike-devel-request(a)lists.lysator.liu.se ha escrit: > Send Pike-devel mailing list submissions to > pike-devel(a)lists.lysator.liu.se > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.lysator.liu.se/mailman/listinfo/pike-devel > or, via email, send a message with subject or body 'help' to > pike-devel-request(a)lists.lysator.liu.se > > You can reach the person managing the list at > pike-devel-owner(a)lists.lysator.liu.se > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pike-devel digest..." > > > Today's Topics: > > 1. pike under sanitizers (Mike) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 23 Jan 2020 10:40:13 +0000 > From: "Mike" <tankf33der(a)disroot.org> > To: pike-devel(a)lists.lysator.liu.se > Subject: pike under sanitizers > Message-ID: <96b4ff652af97bf1d5d49b78dd71f602(a)disroot.org> > Content-Type: text/plain; charset="utf-8" > > hi all, > > I've compiled and run tests by clang with different sanitizers (address, memory, undefined). > If somebody wants to get report(s) and fix let me know. Some of them are trivial and make sense. > I'm already post announce on irc and sent mail to grubba@ without reply :) > > (mike) > > > End of Pike-devel Digest, Vol 173, Issue 3 > ******************************************

2 1

pike under sanitizers
by Mike 23 Jan '20

23 Jan '20

hi all, I've compiled and run tests by clang with different sanitizers (address, memory, undefined). If somebody wants to get report(s) and fix let me know. Some of them are trivial and make sense. I'm already post announce on irc and sent mail to grubba@ without reply :) (mike)

1 0

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

Jump to page:

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