Pike-devel December 2011

pike-devel@lists.lysator.liu.se

3 participants
7 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 28 Feb '26

28 Feb '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

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

configure.in question: compiler but not ld flags
by H. William Welliver III 22 Dec '11

22 Dec '11

When adding configure tests, where does one place flags intended for the compilation phase but not the linking phase? The flag I need to add (-x objective-c) doesn't seem like it should be a problem, but for some reason, using it when linking causes gcc to enter compile mode, rather than linking mode. Right now, it appears that adding items to either CFLAGS or CPPFLAGS, they all end up in LD (CFLAGS directly, and CPPFLAGS via DEFINES). It seems to me that CPPFLAGS and LDFLAGS should be independent of each other (though I imagine it might occur that certain flags are used in both modes). Bill

5 10

Countdown to new 7.8 release
by H. William Welliver III 16 Dec '11

16 Dec '11

Hello all, I'd like to start the gears turning on the process that will eventually spit out a new 7.8 release. Since I'm new to the process, I'll probably need Peter to show me the ropes. Hopefully he'll see this note and will throw together a brief guide for me and anyone else interested in the release process. While waiting for the process to be revealed to me, I've started sifting through the commit log to get a rough draft of the release notes. There will probably be a need for some clarification, so expect to be getting a note from me in the near future. Finally, you should take this message as notice of an impending change freeze on the 7.8 tree. If you have any undelivered changes, please get them in within the next week. Once the release process kicks off, I'd like to limit commits to the 7.8 tree to build/traffic-light related fixes. As always, any comments or suggestions are welcome! Bill

4 3

kqueue based file event notification and the backend
by Bill Welliver 01 Dec '11

01 Dec '11

I've taken a cue from Arne's inotify module and have started working on one for kqueue based systems. The code basically works but suffers from a (imho) major drawback: it's not integrated with the Pike backend. The inotify code slides nicely into the backend, primarily because inotify presents itself as a standard fd with a read data event to indicate events. kqueue, however, uses different event types monitored by kqueue. Right now, a secondary kqueue loop can be run in a thread to wait for events, but that seems pretty ugly to me. I'd like to find a better approach. An alternate approach might be to hook a second, immediate-timeout call to kqueue() into the backend, similar to the GTK or ObjectiveC module. That's a little better, as at least the end user sees a more consistent approach to asynchronous events. Internally, I think it probably at least less efficient, with other possible drawbacks. I think the nicest approach would be to modify the kqueue backend so that it can register VNODE, PROC and SIGNAL filters and shunt them off to an appropriate handler. That, however, means that the backend would be split again (creating a KqueueBackend or similar), with the new implementation having different features. If anyone's interested in looking at the code, it's available here: https://bitbucket.org/hww3/public_system_kqueue/ I should note that I've commited some changes today away from my development box, so it's likely that the last few revisions have errors in them. Does anyone else have thoughts about these approaches (or have an alternate one?) Perhaps I've missed something obvious... it wouldn't be the first time! Best, Bill

3 3

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 December 2011