Pike-devel October 2013

pike-devel@lists.lysator.liu.se

5 participants
5 discussions

debugger opcodes
by Bill Welliver 30 Oct '14

30 Oct '14

I noticed that folks have been working on code generation lately. Any chance it might be possible to implement some of the opcodes required to get debugging working (step, break, etc)? I seem to recall someone indicating it wasn't a terribly difficult task, but it's clearly beyond my understanding of the problem. Bill

4 6

Sql.pgsql behavior in case of errors
by aldem-pikedev＠aldem.net 21 Aug '14

21 Aug '14

Hi everyone, I am preparing to use Postgres in my app, found the following strange behavior: ---snip--- Sql.Sql db = Sql.Sql("pgsql://localhost", "test", "test", "test"); db->query("BEGIN"); db->query("INSERT INTO requests (SvTrId) VALUES ('lala')"); catch(db->query("INSERT INTO requests (SvTrId) VALUES ('lala')")); db->query("INSERT INTO requests (SvTrId) VALUES ('juju')"); db->query("ROLLBACK"); ---snip--- Database is opened, row with 'lala' is inserted, second query (obviously) fails as SvTrId is the primary key, but row with 'juju' is inserted *and* appears in the database - i.e. the transaction is *committed*! Studying source code show, that once error is encounter, session is reset, i.e. running transaction is rolled back, everything is closed, temporary tables are deleted and session variables are reset as well, and after that, the next statement(s) will be committed immediately, as there is no active transaction. In my opinion, this is not exactly correct behavior when statement fails, as session still may be needed (especially temporary tables, open cursors etc). Im some cases, this is perfectly normal when SQL statement fails, especially in SERIALIZED transaction isolation level, and it would be more practical to leave the decision as of what to do to the application. Yes, this is true that it is impossible to continue executing statements in failed transaction, but temporary tables etc. may still be needed. Also, silent reconnection is not a good idea too - when there are many transactional statements are executed - it would be nice to have an option to modify this behavior. Best regards, /Alexander

5 6

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

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 October 2013