Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Pike Users & Developers Conference 2013
by H. William Welliver III 05 Oct '13

05 Oct '13

The 2013 edition of the Pike Users and Developers Conference will be held November 1st through 3rd in Linköping, Sweden. As always, I expect this will be a great opportunity to find out what's been happening in the Pike community as well as to help shape the future of everyone's favorite language. More details and the registration form may be found at the following URL: http://pike2013.webhaven.eu Please feel free to contact me with any comments, questions or suggestions for the program(me). Bill

1 0

build failure on Windows
by Peter Bortas 03 Oct '13

03 Oct '13

I'm trying to boot up my old Windows build environment, and I'm getting a new and exiting build error from master. Haven't looked at the code, but will do that tomorrow night if no one has done it before then: #### Making static: modules/_Stdio Compiling modules/_Stdio/udp.c B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(393) : error C2065: 'IPPROTO_IPV6' : undeclared identifier B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(440) : error C2065: 'IPPROTO_IPV6' : undeclared identifier B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(504) : error C2065: 'IPPROTO_IPV6' : undeclared identifier B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(590) : error C2065: 'IPPROTO_IPV6' : undeclared identifier CL returned error code 2. WARNING: Compiler failure! Trying without optimization! B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(393) : error C2065: 'IPPROTO_IPV6' : undeclared identifier B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(440) : error C2065: 'IPPROTO_IPV6' : undeclared identifier B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(504) : error C2065: 'IPPROTO_IPV6' : undeclared identifier B:\dists\Pike-v7.9-snapshot\src\modules\_Stdio\udp.c(590) : error C2065: 'IPPROTO_IPV6' : undeclared identifier CL returned error code 2. Compilation command was: /home/builder/dists/Pike-v7.9-snapshot/bin/smartlink rntcl -I. -I/home/builder/dists/Pike-v7.9-snapshot/src/modules/_Stdio -I/home/builder/dists/Pike-v7.9-snapshot/build/windows_xp-5.1.2600-i386 -I/home/builder/dists/Pike-v7.9-snapshot/src -Dpike_module_init=pike_module__Stdio_init -Dpike_module_exit=pike_module__Stdio_exit -DHAVE_CONFIG_H -g -MD -c /home/builder/dists/Pike-v7.9-snapshot/src/modules/_Stdio/udp.c -o udp.o make[6]: *** [udp.o] Error 2 make[5]: *** [all] Error 2 make[4]: *** [_Stdio] Error 1 make[3]: *** [static_module_objects] Error 1 make[2]: *** [module_objects] Error 2 make[1]: *** [_make_in_builddir] Error 2 make: *** [wix] Error 2 -- Peter Bortas

5 10

Parser.XML Node walking broken?
by Bill Welliver 27 Sep '13

27 Sep '13

I'm having trouble with some code that works in 7.8.700: int main(int argc, array argv) { string xml = "<?xml version=\"1.0\"?><foo><bar> <gazonk/></bar></foo>"; object r = Parser.XML.NSTree.parse_input(xml); r[1]->walk_inorder(lambda(mixed n){ werror("n: %O\n", n); }); return 0; } yields: n: Parser.XML.NSTree.NSNode(TEXT) Cannot index float with "walk_inorder". /usr/local/pike/7.9.11/lib/modules/Parser.pmod/XML.pmod/Tree.pmod:470: Parser.XML.NSTree.NSNode(TEXT)->walk_inorder(/main()->__lambda_65675_0_lin e_5) /usr/local/pike/7.9.11/lib/modules/Parser.pmod/XML.pmod/Tree.pmod:465: Parser.XML.NSTree.NSNode(ELEMENT,"bar",0)->walk_inorder(@0=/main()->__lamb da_65675_0_line_5) /usr/local/pike/7.9.11/lib/modules/Parser.pmod/XML.pmod/Tree.pmod:465: Parser.XML.NSTree.NSNode(ELEMENT,"foo",0)->walk_inorder(@0) test.pike:5: /main()->main(1,({"/home/hww3/test.pike"})) I've noticed similar problems with the other walk functions, as well. Bill

1 0

bug in Protocols.XMLRPC
by Martin Bähr 21 Aug '13

21 Aug '13

Protocols.XMLRPC contains the following: protected mixed decode(string xml_input, string dtd_input, int|void boolean) { // We cannot insert 0 integers directly into the parse tree, so // we'll use magic_zero as a placeholder and destruct it afterwards. object magic_zero = class {}(); ... case "int": return (int)(data*"") || magic_zero; ... destruct(magic_zero); // Apply Magic! Replace magic_zero with real 0:s. unfortunately this doesn't quite work: Pike v7.9 release 5 running Hilfe v3.5 (Incremental Pike Frontend) > object magic_zero = class {}(); > mapping foo = ([ "foo":magic_zero ]); > destruct(magic_zero); Compiler Warning: 1: Returning a void expression. Converted to zero. (1) Result: 0 > foreach(foo; string key; mixed val){ write("%O\n", intp(val)); } 0 Ok. in other words, in this situation, the magic zero is not recognized as an int. this causes for example xml-rpc-call in modules/tags/additional_rxml.pike to fail: format_response: else if (intp (val)) buf->add ("<int>", (string) val, "</int>\n"); ... else { // Gotta be a Calendar object. // Format this to be compatible with the iso-time attribute // to the <date> tag. buf->add ("<iso-date-time>", val->format_time(), "</iso-date-time>\n"); } failing with: Internal server error: Lookup in destructed object.

2 1

String clearing
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 16 Aug '13

16 Aug '13

Per and I discussed the recent string clearing changes and think that most of them should be rolled back. Having clear on exit set on all random strings, random seeds and all decrypted data is often not needed. Having the flag propagade through string operations is probably also not desired in the general case.

7 13

Re: String clearing
by Per Hedbor () ＠ Pike (-) developers forum 16 Aug '13

16 Aug '13

However, your test is more likely to benchmark the function call, not the clearing of the string.

1 0

Benchmark output
by Per Hedbor () ＠ Pike (-) developers forum 16 Aug '13

16 Aug '13

Is anyone seriously attached to the current pike -x benchmark format/output? I have done some work to a: Only output relevant information b: Actually output relevant information. Additionally I have added a json output mode, and a way to run a benchmark with an old result as the baseline (and then report differences, useful when you are trying to optimize something). What is left of the output is somewhat sparse, though. The perhaps most important part that is missing is the memory usage, but it was rather .. random before, since it counted the memory use _after_ the benchmark was run. # leopard$ make benchmark BENCHARGS="-c $PWD/compare" (...) ----------------------------------------------------------------- Test Result Change ----------------------------------------------------------------- Ackermann . . . . . . . . . . . . . . . . . . . . . 38M/s -0.1% Append array . . . . . . . . . . . . . . . . . . . 23M/s -0.1% Append mapping (+) . . . . . . . . . . . . . . . 4902k/s 0.2% Append mapping (|) . . . . . . . . . . . . . . . 5571k/s 6.3% Append multiset . . . . . . . . . . . . . . . . . . 105k/s -3.3% Array & String Juggling . . . . . . . . . . . . . . 110k/s -4.8% Array Copy . . . . . . . . . . . . . . . . . . . . 41M/s 2.0% Array Zero . . . . . . . . . . . . . . . . . . . . 285k/s 0.0% Binary Trees . . . . . . . . . . . . . . . . . . . 994k/s 3.3% Clone null-object . . . . . . . . . . . . . . . . . 11M/s 1.1% Clone object . . . . . . . . . . . . . . . . . . 5627k/s -9.4% Compile . . . . . . . . . . . . . . . . . . . 97k lines/s -0.1% Compile & Exec . . . . . . . . . . . . . . . 92k lines/s -0.3% Foreach (arr,global) . . . . . . . . . . . . . . . 71M/s -2.6% Foreach (arr,local) . . . . . . . . . . . . . . . . 174M/s 1.4% Foreach (arr;local;global) . . . . . . . . . . . . 37M/s -1.1% Foreach (arr;local;local) . . . . . . . . . . . . . 52M/s 1.0% GC . . . . . . . . . . . . . . . . . . . . . . . . 1197/s 2.2% Insert in array . . . . . . . . . . . . . . . . . . 48M/s 0.4% Insert in mapping . . . . . . . . . . . . . . . . . 10M/s -2.2% Insert in multiset . . . . . . . . . . . . . . . 3868k/s 2.4% Loops Nested (global) . . . . . . . . . . . . . . . 31M/s 2.9% Loops Nested (local) . . . . . . . . . . . . . . . 181M/s -0.4% Loops Nested (local,var) . . . . . . . . . . . . . 161M/s -2.0% Loops Recursed . . . . . . . . . . . . . . . . . . 18M/s 1.1% Matrix multiplication (100x100) . . . . . . . . 2.23 GF/s 1.9% Read binary INT128 . . . . . . . . . . . . . . . . 197k/s -0.9% Read binary INT16 . . . . . . . . . . . . . . . . . 19M/s 20.1% Read binary INT32 . . . . . . . . . . . . . . . . . 17M/s -2.0% Replace (parallel) . . . . . . . . . . . . . . . . 9831/s 5.0% Replace (serial) . . . . . . . . . . . . . . . . . 13k/s -2.6% Sort equal integers . . . . . . . . . . . . . . . . 59M/s -0.9% Sort ordered integers . . . . . . . . . . . . . . . 88M/s -0.1% Sort unordered integers . . . . . . . . . . . . . . 14M/s 3.9% Sort unordered objects . . . . . . . . . . . . . . 569k/s -2.2% String Creation . . . . . . . . . . . . . . . . . 3053k/s -8.1% String Creation (existing) . . . . . . . . . . . . 10M/s 1.9% String Creation (wide) . . . . . . . . . . . . . . 678k/s 1.9% Tag removal u. Parser.HTML . . . . . . . . . . . 4929k/s 3.5% Tag removal u. Regexp.PCRE . . . . . . . . . . . 2124k/s 1.4% Tag removal u. array_sscanf . . . . . . . . . . . 6150k/s -0.2% Tag removal u. division . . . . . . . . . . . . . 3113k/s -1.5% Tag removal u. search . . . . . . . . . . . . . . 5218k/s -2.9% Tag removal using a loop . . . . . . . . . . . . . 895k/s -2.3% Tag removal using sscanf . . . . . . . . . . . . . 718k/s 2.7% Upper/lower case shift 0 . . . . . . . . . . . . . 137M/s -0.3% Upper/lower case shift 1 . . . . . . . . . . . . . 60M/s -1.4% call_out handling . . . . . . . . . . . . . . . . . 177k/s 0.2% call_out handling (with id) . . . . . . . . . . . 4560k/s -2.4% ----------------------------------------------------------------- 0.3% -----------------------------------------------------------------

5 6

Calender question.
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 14 Aug '13

14 Aug '13

If you create a Day and call next() it will not have all fields calculated. It looks intentional, but is it useful? Pike v7.9 release 11 running Hilfe v3.5 (Incremental Pike Frontend) > object d = Calendar.ISO.Day(2013,8,14); > object e = d->next(); > e->md; (1) Result: -1000 > e->m; (2) Result: -1000 > e->make_month(); (3) Result: 0 > e->md; (4) Result: 15 > e->m; (5) Result: 8 or to put it in more surprising terms > object d = Calendar.ISO.Day(2013,8,14)->next(); > d->m; (1) Result: -1000 > d; // Forces _sprintf to call make_month() (2) Result: Day(Thu 15 Aug 2013) > d->m; (3) Result: 8

2 3

beginning a new Pike 7.8 release cycle
by Bill Welliver 12 Jul '13

12 Jul '13

It's been a bit over 9 months since the last 7.8 release, and a number of fixes have been applied to the 7.8 tree. Therefore, I'd like to begin the process of making another 7.8 stable release. I will begin working on the changelog during the next week; once that's complete, I'll cut an alpha release for review and consideration. If you've been saving any bugfixes for 7.8, please start thinking about getting those committed. Thanks! Bill

1 0

Thread deprecation
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 09 Jul '13

09 Jul '13

The deprecation of Thread->`() doesn't look to work as it should. bin/pike -e Thread lib/modules/Thread.pmod:9: Warning: Using deprecated function(mixed, mixed ... : { Thread = object(implements _static_modules.Builtin()->thread_id) }) value. lib/modules/Thread.pmod:10: Warning: Using deprecated function(mixed, mixed ... : { Thread = object(implements _static_modules.Builtin()->thread_id) }) value.

2 1

Jump to page:

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