Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

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 08 Jan '19

08 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

Thread.ResourceCount: Fixed mutex handling.
by Stephen R. van den Berg 08 Dec '18

08 Dec '18

commit d168eb73a23756642bdc80451ba206a345471f6a Author: Henrik Grubbström (Grubba) <grubba(a)grubba.org> Date: Sun Aug 5 11:21:52 2018 +0200 Thread.ResourceCount: Fixed mutex handling. I'm not saying that this is not correct, I just want to make sure I understand the change. Can anyone elaborate on as to why this change is necessary/desirable? -- Stephen.

2 4

debugger, status and suggestions sought
by H. William Welliver III 07 Dec '18

07 Dec '18

Hi all, After a helpful conversation at the pike meet-up last month, I’ve been working on a proof-of-concept debugger for pike code. There is a lot of work left to do, and hopefully others will help me out, but I think that things are at a point where it can be used to do actual debugging. I’ve put together a page[1] with my notes (and the code contains a lot of TODOs as well). Please take a look at both the page and the branch (bill/debugger-poc) and let me know if you think there are glaring faults in the approach. I am certain that there are a lot of small bugs as well. Please feel free to dig in and help out. I suspect that a lot of the work to be done won’t really make a lot of sense until there’s a debugging client to use it with (beyond the hilfe I’ve been testing with). There are a few items that I think I probably need guidance with: 1. Local names aren’t available. Previously, I attempted to parse these out of the source code, but I suspect that’s a losing battle. 2. I was chatting with Mateusz and we were thinking that something that gave us access to the parse tree might be helpful for clients. I wrote a Pike parser in java that is used by the eclipse plugin I wrote, and this allowed generating useful navigation and variable data. Would a native pike equivalent be useful for this and things such as a hypothetical Language Server Protocol? Maintaining duplicate code is probably not the best use of our time; but I suspect that the existing source isn’t really set up to allow this sort of piggy-back use. As always, feedback and suggestions are welcome! Bill [1] http://wiki.gotpike.org/index.pike/PikeDevel/PikeDebugger

4 6

line number storage and included files
by H. William Welliver III 26 Nov '18

26 Nov '18

Hi all, I’ve been looking at the linenumbers element in struct program as a means of getting offsets for a given line number. Since a program can be made up of multiple files through includes, I need to make sure that when I look through the entries, that I’m only comparing line numbers that come from the file I’m interested in. The initial file marker entry appears correctly, however, when the file changes, a new marker entry doesn’t seem to be inserted in the array. I see that the line numbers jump correctly, but there is no other indication that the source of the lines has changed. Is this intentional, or am I missing something? Here’s an example tracing through a program with a file included within a function definition. cnt: 127 <— beginning of program new file file: /Users/hww3/bpt.pike cnt: 0 line: 0 0x0 cnt: 36 line: 2 0x24 cnt: -127 line: 4 0xcd cnt: 54 line: 5 0x103 cnt: -127 line: 8 0x1ab cnt: -127 line: 9 0x23e cnt: 34 line: 10 0x260 cnt: 116 line: 12 0x2d4 cnt: -127 line: 14 0x37d cnt: 69 line: 15 0x3c2 cnt: -127 line: 16 0x467 cnt: -127 line: 18 0x52c cnt: -127 line: 19 0x5ff cnt: 76 line: 1 0x64b <— included file, line number jumps to 1, but no marker cnt: 114 line: 2 0x6bd cnt: 80 line: 21 0x70d <— back to original file, but also no marker cnt: -127 line: 22 0x7a6

4 10

Should atexit really store a weak reference?
by ceder (-) Per Cederqvist ＠ Pike (-) developers forum 23 Nov '18

23 Nov '18

The atexit() function internally stores the exit handlers in "atexit_functions" (see src/signal_handler.c). For some reason I don't understand, f_atexit() includes this line: atexit_functions->flags |= ARRAY_WEAK_FLAG; This means that if you pass a lambda to atexit() and don't hold any other references to the lambda, it may be garbage collected. This is not documented, and I belive it is bad. At the very least, it is not what I expected. Here is a sample program. Note that is doesn't print "atexit lambda 0.200 running" unless you remove the gc call. --- cut here --- #!/usr/bin/env pike void do_exit() { werror("do_exit function running\n"); exit(0); } void setup_lambda(float x) { atexit(lambda() { werror("atexit lambda %f running\n", x); } ); } int main() { call_out(setup_lambda, 0.2, 0.2); call_out(gc, 0.4); call_out(setup_lambda, 0.6, 0.6); call_out(do_exit, 0.8); return -1; }

2 1

Pike sites downtime tomorrow, Saturday Nov 17
by Peter Bortas 16 Nov '18

16 Nov '18

All Pike sites will go down while the machines are moved a few racks over. The downtime will be somewhere between 09:00 and 18:00 and is estimated to last less than 60min. This is done together with a lot of other machines, so a more exact timeline is not possible. Regards, -- Peter Bortas

1 0

Pike 8.0.702 release candidate
by Peter Bortas 12 Oct '18

12 Oct '18

Pike 8.0.702 release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.702/Pike-v8.0.702.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.702/Pike-v8.0.702-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.702/Pike-v8.0.702-win32-oldli… Changes since Pike 8.0.610 (release 12) New Features ------------ o Sql.mysql In unicode decode mode, characters outside the BMP are now encoded as UTF-8 encoded UTF-16. This works around that MySQL/MariaDB don't allow characters outside the BMP in utf8 strings (and instead require the character set to be declared as utf8mb4, which has quite a few side effects). Bug fixes --------- o Runtime - Fixed NULL dereference (SIGSEGV) in _disable_threads() if another thread is holding the compiler lock. - Fixed loss of Pike_interpreter_pointer (race, --with-debug only). The Pike_interpreter_pointer must not be altered by threads not holding the interpreter lock... o Calendar - Updated tzdata to 2018e. o Compiler - The machine code generator for ppc64 now generates correct code under ABI v2 (ppc64le) - Fixed an incompatibility between the machine code generator on ppc and GCC 7. - Support inherit of CompilerEnvironment. Fix some bugs triggered in the supporter subsystem when executing in an inherited CompilerEnviroment. o Filesystem.Monitor - Fix NULL-dereference in bump(). Survive st being zero in bump(). o Fuse - Switched the Fuse module to use a different libfuse API. The way we used to use libfuse got first deprecated and support for it is now removed from the libfuse git repository entirely. In addition, our previous use of said libfuse API triggered a bug resulting in a segmentation fault in at least libfuse 2.9.2 and 2.9.7. We now use libfuse in a less elegant but more usual way, and do not trigger the bug anymore. - Handle errors in Fuse operations (i.e. Pike code implementing FUSE filesystems) gently by reporting ENOSYS instead of exiting the process. o Gmp.mpq Fix numbers between -1.0 and 1.0 sometimes missing a leading 0. o Pike.identify_cycle Fix various issues with LFUNs throwing errors. LFUNs used by mapping operations may throw errors; this caused identify_loop_visit_leave() to also throw errors. The rest of the identify_cycle code was not happy about this and - Forgot to unlock the mc_mutex. This caused all following calls to Pike.identify_cycle() and Pike.count_memory() to hang. - Leaked memory. The above issues are now avoided by instead using the addresses of objects as indices in the affected mapping. It also fixes the issue with hangs if there are objects with lfuns calling Pike.identify_cycle() or Pike.count_memory(). o Protocols.HTTP.Server Fix an issue with accounting of sent bytes that caused responses to requests over HTTPS to not finish on success, but instead the whole connection to time out. Data for the first request was usually fully written, but the connection neither was properly closed nor re-used. o Protocols.WebSocket - Added low_connect() and low_websocket_accept(). These make it easier to test the error handling in the module, and to replace the HTTP-layer. - Improved compliance with RFC 6455 section 4.1. o The nonce is now actually random. o The http version, method and headers are validated. o Header case-sensitivity issues have been fixed. - The module now has a testsuite. - Improved HTTP-header camel-case consistency. o Sass - Errors thrown by handle_sass_import() can now be caught and handled by the caller of compile_file() and compile_string(). - Added the option "sass_syntax". This option will parse the input as having indented Sass syntax. This option only has effect in compile_string(). - Added method sass2scss() to convert Sass syntax to SCSS syntax. o Sql.pgsql - Fix regression bug since rel 12 that hangs queries returning over 1024 records. - Fix all rare-deadlock-causes logged in the last two years. o Stdio.Buffer Eliminate race condition in read_cstring(). o Stdio.UDP Fixed wait() failing with ENOTSOCK on NT. o Thread.Farm - Fixed lost error in provide_error() exception handling. - Avoid delayed deallocation of jobs by clearing references immediately after execution. o Tools.Standalone - extract_autodoc: Terminate on failure. Reenable termination on extraction failure. Building & Tools ---------------- o Java - The location of libjvm is now detected on Ubuntu 18.04. - Detect and support OpenJDK 10. o Postgres Support Postgresql 10 and later. o Sass Improved detection of C++ runtime library on MacOS X. MVH, -- Peter Bortas

3 3

Pike 8.0.690 beta/release candidate
by Peter Bortas 12 Sep '18

12 Sep '18

Pike 8.0.690 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.690/Pike-v8.0.690.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.690/Pike-v8.0.690-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.690/Pike-v8.0.690-win32-oldli… Changes since Pike 8.0.610 (release 12) New Features ------------ o Sql.mysql In unicode decode mode, characters outside the BMP are now encoded as UTF-8 encoded UTF-16. This works around that MySQL/MariaDB don't allow characters outside the BMP in utf8 strings (and instead require the character set to be declared as utf8mb4, which has quite a few side effects). Bug fixes --------- o Runtime - Fixed loss of Pike_interpreter_pointer (race, --with-debug only). The Pike_interpreter_pointer must not be altered by threads not holding the interpreter lock... o Calendar - Updated tzdata to 2018e. o Compiler - The machine code generator for ppc64 now generates correct code under ABI v2 (ppc64le) - Fixed an incompatibility between the machine code generator on ppc and GCC 7. - Support inherit of CompilerEnvironment. Fix some bugs triggered in the supporter subsystem when executing in an inherited CompilerEnviroment. o Filesystem.Monitor - Fix NULL-dereference in bump(). Survive st being zero in bump(). o Fuse - Switched the Fuse module to use a different libfuse API. The way we used to use libfuse got first deprecated and support for it is now removed from the libfuse git repository entirely. In addition, our previous use of said libfuse API triggered a bug resulting in a segmentation fault in at least libfuse 2.9.2 and 2.9.7. We now use libfuse in a less elegant but more usual way, and do not trigger the bug anymore. - Handle errors in Fuse operations (i.e. Pike code implementing FUSE filesystems) gently by reporting ENOSYS instead of exiting the process. o Gmp.mpq Fix numbers between -1.0 and 1.0 sometimes missing a leading 0. o Pike.identify_cycle Fix various issues with LFUNs throwing errors. LFUNs used by mapping operations may throw errors; this caused identify_loop_visit_leave() to also throw errors. The rest of the identify_cycle code was not happy about this and - Forgot to unlock the mc_mutex. This caused all following calls to Pike.identify_cycle() and Pike.count_memory() to hang. - Leaked memory. The above issues are now avoided by instead using the addresses of objects as indices in the affected mapping. It also fixes the issue with hangs if there are objects with lfuns calling Pike.identify_cycle() or Pike.count_memory(). o Protocols.HTTP.Server Fix an issue with accounting of sent bytes that caused responses to requests over HTTPS to not finish on success, but instead the whole connection to time out. Data for the first request was usually fully written, but the connection neither was properly closed nor re-used. o Sass - Errors thrown by handle_sass_import() can now be caught and handled by the caller of compile_file() and compile_string(). - Added the option "sass_syntax". This option will parse the input as having indented Sass syntax. This option only has effect in compile_string(). - Added method sass2scss() to convert Sass syntax to SCSS syntax. o Sql.pgsql - Fix regression bug since rel 12 that hangs queries returning over 1024 records. - Fix all rare-deadlock-causes logged in the last two years. o Stdio.Buffer Eliminate race condition in read_cstring(). o Thread.Farm - Fixed lost error in provide_error() exception handling. - Avoid delayed deallocation of jobs by clearing references immediately after execution. o Tools.Standalone - extract_autodoc: Terminate on failure. Reenable termination on extraction failure. Building & Tools ---------------- o Java - The location of libjvm is now detected on Ubuntu 18.04. - Detect and support OpenJDK 10. o Postgres Support Postgresql 10 and later. Regards, -- Peter Bortas

1 0

Pike conference 2018
by Tobias S. Josefowitz 07 Sep '18

07 Sep '18

Hi, we invite you to this year's Pike developer conference on the weekend of the 3rd and 4th of November 2018. Opera Software will host the conference in its offices in Linköping. On Saturday and Sunday we meet at the Opera offices (Repslagaregatan 21) starting from 10:00. Just call "Opera Software" using the fancy door-bell-replacement technology at the entrance (or follow instructions as posted on the door). If you intend to join, please consider dropping me an email to let me know. You are also most welcome to send me an email in case you have any other questions. In case you want to schedule an agenda item for the conference, please also just send me an email. On behalf of the 2018 conference committee, Tobi

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