Pike-devel June 2014

pike-devel@lists.lysator.liu.se

4 participants
17 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 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

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

Build fail
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 27 Jun '14

27 Jun '14

Did you run ./run_autoconfig ? It seems configure thinks that its a good idea to rerun the main script in subdirectories that don't have their own configure scripts...

1 0

Re: Casting int to float broken in 8.0 on amd64 Linux
by Chris Angelico 25 Jun '14

25 Jun '14

On Tue, Jun 24, 2014 at 7:05 PM, Per Hedbor () @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Could you give this version of SET_SVAL a try, perhaps? > > #define SET_SVAL(SVAL, TYPE, SUBTYPE, FIELD, EXPR) do { \ > /* Set the type afterwards to avoid a clobbered \ > * svalue in case EXPR throws. */ \ > struct svalue * _sv_ptr=&( SVAL ); \ > _sv_ptr->u.FIELD = (EXPR); \ > *((ptrdiff_t*)&_sv_ptr->type) = TYPE_SUBTYPE(TYPE,SUBTYPE);\ > } while(0) Has exactly the same result. It's entirely possible I'm misdiagnosing this. To come to the conclusion I did, I took the current 8.0 branch, reverted that one commit, and then began applying it piece by piece. The change to configure.in didn't break anything, the change to svalue.h did. Within that, changing from INT16 to short had no effect (on my system, I believe INT16 compiles to short anyway); adding structures and unused defines, unsurprisingly, didn't break anything; and changing the definition of SET_SVAL induced the error message. That's all the info I have to offer. I'm starting up a completely fresh Pike clone to see if somehow I've accumulated cruft of some sort. If that behaves differently, I'll let you know. ChrisA

5 6

new 7.8 stable
by Bill Welliver 24 Jun '14

24 Jun '14

I've moved the latest 7.8 (7.8.866) build to the "all" directory and created a symbolic link to latest-stable. Please feel free to download and upload binaries if you're into such things. Do let me know if any problems are discovered... if all goes well I'll announce things on the main mailing list sometime tomorrow. Best, Bill

1 0

Casting int to float broken in 8.0 on amd64 Linux
by Chris Angelico 24 Jun '14

24 Jun '14

As of commit 7666f806, casting an int to a float fails: rosuav@sikorsky:~/pike$ bin/pike Pike v8.0 release 3 running Hilfe v3.5 (Incremental Pike Frontend) > (float)1; Cast failed, wanted float, got int HilfeInput:1: HilfeInput()->___HilfeWrapper() This happens also on any arithmetic operation that mixes int and float, which does an equivalent cast implicitly. Fiddling around with the corresponding code suggests it may be connected to the GCC warning that also comes up: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] In SET_SVAL, two pointers to the same object with different types are used. I think this violates the C standard, which is why sometimes stuff isn't getting correctly written out - something's getting optimized away. Is there a way to do the same job with a union inside struct svalue, instead of the pointer casts? Or alternatively, can the compiler be told not to optimize this out? ChrisA

2 1

Re: Float details
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 22 Jun '14

22 Jun '14

In e.g. C you would use the signbit() function to find that out. It looks like the Pike sgn() function isn't usable for this purpose though.

1 0

Re: Float details
by Chris Angelico 21 Jun '14

21 Jun '14

On Sat, Jun 21, 2014 at 9:45 AM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > 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 >> -0.0 < 0.0; > (4) Result: 0 These look fine. IEEE 754 says that negative and positive zero are equal. >> decode_value(encode_value(-0.0)); > (3) Result: 0.0 This is the only one that could be called wrong. I doubt it's going to have tripped people up, so changing it or not changing it could be simply a matter of convenience. ChrisA

1 0

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