Pike-devel December 2013

pike-devel@lists.lysator.liu.se

3 participants
6 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.lysator access
by H. William Welliver III 02 Jan '14

02 Jan '14

I've got a pike 7.8 alpha prepared, but I'm having trouble logging in to pike.lysator.liu.se. Can someone with access verify my account (bill) and key? I'm still able to access the server at liu, so if that key can be used, that'd be helpful. Bill

2 1

pre files for gtk
by Per Hedbor () ＠ Pike (-) developers forum 09 Dec '13

09 Dec '13

> I was looking at the GTK support in Pike and noticed the wrappers > where some sort of pre-files in src/post_modules/GTKx > > So are these just a special case of mods that new_build_pgtk.pike > generates and not another supported way of writing cmods? These are rather special, and are only handled by the above mentioned build_pgtk.pike It is called from the build-step (from the Makefile), and the output is C-files, not .cmod-files. .cmod did not really exist as such when the module was first written, also it capitalizes on the fact that the GTK API is rather predictable and easy to generate code for, most of the time the function prototypes are more than enough. The output ends up in build/<OS-name>/post_modules/pgtk*.c There is also a wrapper for the glib-introspection API written by Marcus Comstedt that he showed off a year or so ago, I think it was on a branch in git? Anyway, that one can fairly easily be used to use the gtkwebkit widget directly.

4 4

Stack
by Stephen R. van den Berg 05 Dec '13

05 Dec '13

Did someone try this on the Pike codebase already? http://css.csail.mit.edu/stack/ -- Stephen. "As of Postgres v6.2, time travel is no longer supported." -- PostgreSQL Manual

2 1

7.8 Changelog
by H. William Welliver III 04 Dec '13

04 Dec '13

I've just committed a first attempt at a change log for the next 7.8 release. Please take a look and make or suggest any changes you feel appropriate. I'd like to cut an alpha release some time in the next week. Bill

1 0

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