Pike-devel July 2014

pike-devel@lists.lysator.liu.se

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

Possible bug in Gz with latest Pike 7.8.866 Windows?
by Chris Angelico 29 Jul '14

29 Jul '14

Not sure how to diagnose this. Test case: int main() { string zip="E\217Aj\3""1\fE\367s\212OV-\204\\\243\27\310\276(cMF\240X\306\226;8\247\217fh\323\225\340\363y\377\351\272JC\222\312\263[\35\230)\343\306\350\215\23\26\253P\233IQ\264\337%\267""3\266U\346\25T\31\331\34\205\252\303\26\370\312x\220\344\351k\224\326\37\250\\\254\311\316\273\340\272\362\300&\252;V\215R\200iq\256 }\203!\371\r\371\313\246\177\251\217\324\31nQ\t\327\33K\276\207\247j\220N\317\347\367\241x\2\345\24\205\336\320\254\372^Qj\376y\336\363\351\330\317\374\23\253aaq\267*\356\34\277\216(\f\364\222\310\217\215\337\27\304\33\353r\231^"; object infl=Gz.inflate(-15); string data=infl->inflate(zip); write("Inflated %d bytes to %d; end-of-stream ought to be \"\": %O\n",sizeof(zip),sizeof(data),infl->end_of_stream()); } Yeah, that's hardly minimal, sorry. It does seem to be data-dependent. On Pike 8.0 on Linux, this produces: Inflated 185 bytes to 287; end-of-stream ought to be "": "" This is correct. The given byte stream is a complete deflation sequence, and end-of-stream is reached with no additional data. Pike 7.8.866 on Windows (the current .msi) says 0 at the end, instead - implying that it's still looking for more data. I'm no expert on compression algorithms, so I have no idea what's going on here. Is it some kind of weird bug in zlib? ChrisA

2 2

Re: Pike 7.8.866 for Windows
by Peter Bortas 24 Jul '14

24 Jul '14

*checks* No, I'm quite sure the last win32 build I did was 7.8.856. -- Peter Bortas On Wed, Jul 23, 2014 at 11:35 PM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Don't you mean 7.8.866?

1 0

Pike 7.8.866 for Windows
by H. William Welliver III 24 Jul '14

24 Jul '14

After a few weeks of messing around with libraries, I’ve got a windows build of Pike with a reasonably complete set of modules ready for testing. Please have a look and let me know if there are any problems or modules that would be advantageous to add. Pike-v7.8.866-win32.msi Thanks in advance! Bill Software......Pike Version.......Pike v7.8 release 866 WWW...........http://pike.ida.liu.se/ pike binary...c:\Program Files\pikeq\bin\pike.exe master.pike...: c:\Program Files\pikeq\bin/../lib/master.pike Module path...: C:/Program Files/PikeQ/lib/modules Include path..: C:/Program Files/PikeQ/lib/include Program path..: Features......auto_bignum machine_code dynamic_modules threads out-of-band_data COM GL GTK2 Gettext Gmp Gz HTTPAccept Image.FreeType Image.GIF Image.JPEG Image.PNG Image.TIFF Image.TTF Image.XFace Java Java.NATIVE_METHODS MIME Mysql Nettle Odbc PGsql Regexp.PCRE Regexp.PCRE.Widestring SQLite Standards.JSON WhiteFish

4 4

Hello
by Guillaume Collet 23 Jul '14

23 Jul '14

Hi, my name is Guillaume Collet, I'm a french bioinformatician interested in Pike. This message was just to introduce myself. I write C/C++ for for 10 years and I found Pike's features really interesting. That's why I'm here. Cheers, Guillaume.

4 7

Re: Float details
by Mirar ＠ Pike developers forum 09 Jul '14

09 Jul '14

Which serialization? Doesn't ASN.1 have a string format for floats if you want (third byte with value 3 followed by the string)?

2 1

Float details
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 04 Jul '14

04 Jul '14

So -0.0 is a thing. Should we fix any of these: > -0.0; (1) Result: -0.0 > equal(-0.0, 0.0); (2) Result: 1 > decode_value(encode_value(-0.0)); (3) Result: 0.0 > -0.0 < 0.0; (4) Result: 0

2 1

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 2014