Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Pike 8 @ Pike conf 2013
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 16 Nov '13

16 Nov '13

>Consolidated notes from the Pike conference regarding Pike 8. > > Pike 8 branch > ------------- > [/] Update the CHANGES file. > [ ] Make the branch. [...] >As far as I can see, there are no blockers left for making the branch. > >If nobody protests, I'll make the branch later today. And now the branch and Pike 8.0.1 exist: | Pike v8.0 release 1 running Hilfe v3.5 (Incremental Pike Frontend) | >

2 1

PollBackend on OSX
by H. William Welliver III 07 Nov '13

07 Nov '13

I've been playing around with the newest commits to 7.9, in particular a change made that should allow PollDeviceBackend and PollBackend to co-exist. Specifically, I'm trying to get things to compile on OSX, and while I think I've accomplished that goal, it doesn't appear that the resulting PollBackend works (at least all of the tests fail). I seem to remember that being true on OSX, as poll isn't really fully functional. Can anyone confirm that? I don't see any point in committing my my fixes to get both working if the result is non-functional (in which case I'll commit a fix that disables poll on OSX). Bill

2 2

7.9 segfault on 32-bit Darwin
by H. William Welliver III 03 Nov '13

03 Nov '13

Looks like this is the commit that causes 32-bit Pike on Darwin to segfault: commit 20fe37f6c62730993beb1c426c733cb98e12cb44 IA32: Use OPCODE_INLINE_RETURN when compiling with gcc. I've confirmed the problem on OSX 10.7 and 10.8 using gcc-4.2 (supplied by apple). Since machine code currently is a little above my ability to resolve, I'll just leave this as a bug report. Bill

1 0

Pike 7.6 Debian wheezy
by Bertrand LUPART 31 Oct '13

31 Oct '13

Hello, Does someone have (unofficial) pike7.6 packages for Debian wheezy he'd like to share? Thank you, -- Bertrand LUPART 29, rue du Colisée - 75008 Paris +33 1 72 71 71 84

5 10

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

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