Pike-devel March 2014

pike-devel@lists.lysator.liu.se

6 participants
9 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

new 7.8 alpha
by H. William Welliver III 31 Mar '14

31 Mar '14

I’ve uploaded a new 7.8 alpha, incorporating the latest changes for bignum and clang. Please give it a spin. If I don’t hear anything I’ll promote it to beta and make an announcement on the main pike list. Pike-v7.8.852.tar.gz As always, comments and suggestions are welcome. Best, Bill

2 1

Image.FreeType multi face support
by H. William Welliver III 26 Mar '14

26 Mar '14

I’ve attached a diff that adds a new feature to Image.FreeType. I’ve not committed this because some additional work will be required to properly integrate this feature with Image.Fonts. As it stands, the diff should not break compatibility, but it seems possible that proper support in Image.Fonts *might*. Background: Certain font types supported by FreeType can contain multiple faces (be they varying weights or altogether unrelated typefaces) within a single font file. Currently, Image.FreeType and Image.Fonts will simply load the first face in the font file. I’ve noticed that, at least on MacOS X, the first font isn’t always a good default; for example, sometimes it might be a Bold-Oblique variant or whatever. It’d be nice to be able to access the others. The diff makes 2 changes: first, it adds a new field, “face_count”, to the results of Font->info(). The second change is the addition of a second, optional parameter to Font->create(), which allows the face number within the font to be specified. As I mentioned, it’d be nice to include support for this within Image.Fonts, though I’m not sure the best way to handle that. Any suggestions to that end would be welcome. As always, comments and suggestions are welcome. If there are no objections after a time, I’ll commit this change to 8.0. Bill

1 0

compiling the source (VPATH err)
by Danesh Daroui 14 Mar '14

14 Mar '14

Dear all, I have downloaded and compiled successfully the source code of Pike-v7.8.700. Now when I clone the git repository of Pike, the make complains about VPATH is not supported by make. I have modified VPATH variable to point to the where the source code (compiled previously) resides, but the problem is still there. Any tip for that? Regards, D.

4 9

Bignum fixes backported in 7.8
by Jonas Walld�n ＠ Pike developers forum 12 Mar '14

12 Mar '14

I've merged most of the bignum fixes from 8.0 into 7.8 since we need to build with clang on OS X. I've excluded changes that added new API or that removed the AUTO_BIGNUM define and everything passes verbose_verify on my local machine. If you see any unintended side-effects please let me know.

1 0

bash/dash
by Arne Goedeke 10 Mar '14

10 Mar '14

My gentoo /bin/sh (which is bash) unlike dash generates a broken whitespace.h file from the current bin/getwhitespace.sh . I dont know which of the two is wrong here, but should we simply use numeric values instead of character escapes? arne

5 10

segfault: foo[bar]();
by Martin Bähr 03 Mar '14

03 Mar '14

any existing identifier indexed with a non-existing one and then called as a function causes a segfault: mixed foo; foo[bar](); String[int2hex](); fails in 7.8 and 8.0 but not in 7.6 greetings, martin.

1 0

Pike 8
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 02 Mar '14

02 Mar '14

So we are down to two failing testcases, both related to the sprintf type. Can we fix that and release Pike 8 before we break something new?

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 March 2014