Pike-devel July 2012

pike-devel@lists.lysator.liu.se

7 participants
21 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

Packagers?
by Bill Welliver 01 Aug '12

01 Aug '12

Do we have anyone handling Debian packages, or RPMs or the like? I know Grubba does an ebuild but was wondering if there are any others that need to be prepared for a new release? Bill

2 1

New 7.8 release candidate: 7.8.696
by Bill Welliver 01 Aug '12

01 Aug '12

Hello all, I've prepared a new stable release candidate (beta) for everyone's building pleasure. 7.8.696 may be downloaded from: http://pike.ida.liu.se/download/pub/pike/beta/7.8.696/ Please feel free to try it out and please do report back on any success or failures. Best, Bill

5 10

Re: New 7.8 release candidate: 7.8.696
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 31 Jul '12

31 Jul '12

Well, I've uploaded a binary release for Solaris 11 64-bit (should run on OI too), with a working Gettext module. Both libintl and libiconv seems to be the GNU versions (from OpenCSW).

2 7

Pike 7.9
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 30 Jul '12

30 Jul '12

I was looking through the testsuite failures in 7.9. I think that these two are the only two regressions (and possibly the type system ones as well, but that could also be due to grubbas tweaking). int gnu (mixed... args) {}; gnu(@indices (all_constants()), gauge { foreach (({1,2,3}), int j) do if (j && gnu(@indices (all_constants()), 17 + gauge {break;})) return 0; while (0); }); #pragma strict_types void x (void|mapping(string:string) args) { if (args) foreach (indices (args), string a) werror ("%O\n", a); }

1 0

Another minor Filesystem.Base complaint
by Bill Welliver 27 Jul '12

27 Jul '12

Is there a particular reason why the Stat object one gets from a Filesystem.Base object is different than a Stdio.Stat object? In particular, isdir and friends are flags in the Stdio.Stat object, while they're functions in Filesystem.Stat. Bill

2 2

Windows build environment / testing
by Tobias S. Josefowitz ＠ Pike developers forum 27 Jul '12

27 Jul '12

Hey all and Bill, I was wondering if there is any chance of getting hands on a windows build environment for debugging purposes. The nature of the build environment (and lack of windows) does not invite one to set it up himself, but it could be very helpful if we were able to check issues ourselves. Additionally, it would reduce Bill's workload on releases :) Best, Tobi

1 0

CMOD version 4 problem (was Re: CritBit build on Windows)
by H. William Welliver III 24 Jul '12

24 Jul '12

Hi Arne, Thanks… that seems to have resolved that set of errors. Unfortunately, I get a new error. I'm not actually sure it has anything to do with CritBit in particular, but rather the templated CMOD features. Here's the error: Z:/pike-git/src/post_modules/CritBit/redefine.H(54) : error C2010: '.' : unexpected in macro formal parameter list CL returned error code 2. Compilation command was: /Users/hww3/pike-git/bin/smartlink rntcl -I. -I/Users/hww3/pike-git/src/post_modules/CritBit -I/Users/hww3/pike-git/build/windows_xp-5.1.2600-i686 -I/Users/hww3/pike-git/src -IZ:/win32libs/include -I/Users/hww3/pike-git/build/windows_xp-5.1.2600-i686/bundles/include -DHAVE_CONFIG_H -g -MD -DDYNAMIC_MODULE -c /Users/hww3/pike-git/src/post_modules/CritBit/inttree.c -o inttree.o Obviously, redefine.H doesn't have 54 lines, so I dumped the precompiler output. I started looking for the problem but quickly went cross-eyed. I'll try to take a closer look when I'm more fully rested. I put a copy of the file at the following URL if anyone wants to have a look. http://bill.welliver.org/dist/pike/inttree.c.cppout Bill On Jul 23, 2012, at 3:15 AM, Arne Goedeke wrote: > hey bill, > > i think i found the last culprit. hope that fixes it now. > > arne

2 1

CritBit build on Windows
by H. William Welliver III 22 Jul '12

22 Jul '12

I'm in the middle of building Pike 7.9 on windows and am running into a few problems getting CritBit to compile. I've only spent a few minutes looking into the problems, but thought I should report them here, in case anyone has insight into how they should be resolved: 1. Windows doesn't have stdint.h; depending on how heavily CritBit relies on this header, it may be possible to use a substitute file from the following project (it at least shuts the compiler up): http://code.google.com/p/msinttypes/ 2. There seems to be some sort of problem with the generated C code from the new template based CMOD. The .c file was generated by 7.9.5 running on my Darwin system, so it just seems like the MS C compiler (CL.EXE) doesn't like something. I suspect it has something to do with lines like the following: # 1 "src/post_modules/CritBit/inttree.cmod" I've included the error below. Do let me know if I can provide any additional details. Best, Bill Compiling post_modules/CritBit/inttree.c src/post_modules/CritBit/inttree.cmod(1) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(1) : error C2019: expected preprocessor directive, found '2' /usr/local/pike/7.9.5/lib/modules/Tools.pmod/Standalone.pmod/precompile.pike(2739) : error C2019: expected preprocessor directive, found '1' z:\pike-git\src\post_modules\critbit\tree_low.c(185) : warning C4028: formal parameter 2 different from declaration z:\pike-git\src\post_modules\critbit\tree_low.c(365) : warning C4028: formal parameter 1 different from declaration z:\pike-git\src\post_modules\critbit\tree_high.c(46) : warning C4028: formal parameter 2 different from declaration src/post_modules/CritBit/inttree.cmod(39) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/redefine.H(54) : error C2010: '.' : unexpected in macro formal parameter list /Users/hww3/pike-git/src/post_modules/CritBit/redefine.H(61) : error C2019: expected preprocessor directive, found '3' src/post_modules/CritBit/inttree.cmod(41) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_header.H(141) : error C2019: expected preprocessor directive, found '4' src/post_modules/CritBit/inttree.cmod(42) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/iterator_source.H(249) : error C2019: expected preprocessor directive, found '4' src/post_modules/CritBit/inttree.cmod(45) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_source.H(689) : error C2019: expected preprocessor directive, found '4' src/post_modules/CritBit/inttree.cmod(128) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/redefine.H(61) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(130) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_header.H(141) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(131) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/iterator_source.H(249) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(134) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/prefix.H(13) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(135) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_source.H(689) : error C2019: expected preprocessor directive, found '1' CL returned error code 2. WARNING: Compiler failure! Trying without optimization! src/post_modules/CritBit/inttree.cmod(1) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(1) : error C2019: expected preprocessor directive, found '2' /usr/local/pike/7.9.5/lib/modules/Tools.pmod/Standalone.pmod/precompile.pike(2739) : error C2019: expected preprocessor directive, found '1' z:\pike-git\src\post_modules\critbit\tree_low.c(185) : warning C4028: formal parameter 2 different from declaration z:\pike-git\src\post_modules\critbit\tree_low.c(365) : warning C4028: formal parameter 1 different from declaration z:\pike-git\src\post_modules\critbit\tree_high.c(46) : warning C4028: formal parameter 2 different from declaration src/post_modules/CritBit/inttree.cmod(39) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/redefine.H(54) : error C2010: '.' : unexpected in macro formal parameter list /Users/hww3/pike-git/src/post_modules/CritBit/redefine.H(61) : error C2019: expected preprocessor directive, found '3' src/post_modules/CritBit/inttree.cmod(41) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_header.H(141) : error C2019: expected preprocessor directive, found '4' src/post_modules/CritBit/inttree.cmod(42) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/iterator_source.H(249) : error C2019: expected preprocessor directive, found '4' src/post_modules/CritBit/inttree.cmod(45) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_source.H(689) : error C2019: expected preprocessor directive, found '4' src/post_modules/CritBit/inttree.cmod(128) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/redefine.H(61) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(130) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_header.H(141) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(131) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/iterator_source.H(249) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(134) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/prefix.H(13) : error C2019: expected preprocessor directive, found '1' src/post_modules/CritBit/inttree.cmod(135) : error C2019: expected preprocessor directive, found '1' /Users/hww3/pike-git/src/post_modules/CritBit/tree_source.H(689) : error C2019: expected preprocessor directive, found '1' CL returned error code 2. Compilation command was: /Users/hww3/pike-git/bin/smartlink rntcl -I. -I/Users/hww3/pike-git/src/post_modules/CritBit -I/Users/hww3/pike-git/build/windows_xp-5.1.2600-i686 -I/Users/hww3/pike-git/src -IZ:/win32libs/include -I/Users/hww3/pike-git/build/windows_xp-5.1.2600-i686/bundles/include -DHAVE_CONFIG_H -g -MD -DDYNAMIC_MODULE -c /Users/hww3/pike-git/src/post_modules/CritBit/inttree.c -o inttree.o

2 3

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 July 2012