Pike-devel July 2013

pike-devel@lists.lysator.liu.se

2 participants
5 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 03 Dec '25

03 Dec '25

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

3 2

debugger opcodes
by Bill Welliver 31 Oct '14

31 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

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

13 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

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