Pike-devel October 2012

pike-devel@lists.lysator.liu.se

3 participants
12 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

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)?

5 4

managing comport settings in linux
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Not a good idea; the design philosophy of Pike is that Pike-level code should never be able to cause memory corruption at C-level. With ioctls there's no way to know what data a specific ioctl wants without reading the documentation for that specific ioctl for that specific OS. ioctls and fcntls are a way for device handlers to hook in APIs that aren't standard across all filedescriptors. / Henrik Grubbström (Lysator) Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

3 2

full MySQL 4.x support. or pike roadmap
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 01 Mar '26

01 Mar '26

HI to all! mysql 4.x support works only with a mysql CFLAGS=-DUSE_OLD_FUNCTIONS is this correct ? are there plans to make a full 4.x support ? bye, thomas

4 4

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

Feedback on 7.6.132 beta
by H. William Welliver III 29 Oct '12

29 Oct '12

Any feedback on 7.6.132? I think there was some concern about the bundles not working properly, but I think I've identified the likely cause: the 7.6 bundles are old enough that they don't deal with certain ABI combinations well. As a result, the default system/linker ABI is not the same as the selected ABI, so the library ends up not being usable. The configure scripts seem to mask that situation, causing some confusion. The solution is to include a "-arch" argument to LDFLAGS. Since it's unlikely that a simple fix will make that problem go away, I'm not inclined to consider that a blocker. Any thoughts? Bill

1 0

New Pike 7.6 beta: 7.6.132
by H. William Welliver III 19 Oct '12

19 Oct '12

I've prepared a new beta build for 7.6. The build may be downloaded from: http://pike.ida.liu.se/download/pub/pike/beta/7.6.132/Pike-v7.6.132.tar.gz Changes since 7.6.128: - Fixed Stdio.sendfile() on OSX by back porting the appropriate change sets from 7.8. - Included Marcus' changes for inf and nan on OSX when compiling using clang. It's not enough to make everything work, but it's a positive step. - Upgraded bin/export.pike so that it works with git. The export process still has some problems, but it's somewhat improved now. - Updated the year on copyright notices - Change log has been updated As always, please feel free to take a look and get in touch with any problems or concerns. Bill

1 0

7.6 Beta: 7.6.128
by H. William Welliver III 19 Oct '12

19 Oct '12

I've prepared a beta release of 7.6 that contains all of the fixes from the past few years, up through last week. Sadly, it doesn't contain the clang patch that was just committed by mc, but I think it wouldn't have made a big difference in overall clang compatibility. I realize that many people have moved on from 7.6, but there are a number of fixes that would be good to get out, especially for those folks running web servers using pike. Notes: I didn't update the change log, and the export script hasn't been updated for git. http://pike.ida.liu.se/pub/pike/beta/7.6.128/Pike-v7.6.128.tar.gz As always, comments and suggestions are welcome. Best, Bill

3 3

Re: 7.6 Beta: 7.6.128
by Bill Welliver 13 Oct '12

13 Oct '12

I seem to recall the nettle bundle not working properly for me in the past, though I always assumed it had something to do with osx being a little more wonky than other platforms. It seems that, at least in my case, the bundled nettle does get built, but the configure tests fail to find it. I suspect that this has been a problem for quite some time. No idea why the bundled gmp seems to work, though. Bill On 1:54:46 pm 10/11/12 Martin Bähr <mbaehr(a)email.archlab.tuwien.ac.at> wrote: > i am using conary build tools that create a fresh chroot for every > build, so yes, i am sure it's clean, and i removed nettle from the > list of packages installed into the chroot. > > it complains about not finding nettle > > anyways, i solved the problem by getting nettle 1.15 seperately. that > works. > > no idea why the bundle doesn't work.

1 0

Re: pike on osx 10.8 (mountain lion)
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 03 Oct '12

03 Oct '12

I don't have that. I only have macports and it didn't like building me a gcc4.2 for some reason. I'll try to investigate some more once my cold is gone so I can think properly. Another route is also to look into why the LLVM compiler fails. There must be some way we can work around that problem.

1 0

2026

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 October 2012