Pike-devel November 2012

pike-devel@lists.lysator.liu.se

2 participants
10 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

Coverity Scan accounts
by Peter Bortas ＠ Pike developers forum 01 Dec '12

01 Dec '12

After dicussin it on the conferance I contacted Coverity and made a Pike project on their Open Source site. Those of you that want an account to check out and work on the defects it reports please reply to this with the user name and email address you want to use. If you don't want it in the list archives then send it to me directly at bortas(a)gmail.com.

1 1

Readline crash
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 08 Nov '12

08 Nov '12

If I press ´ followed by pretty much any other button in hilfe I get Error decoding [0xb4] using utf8: Invalid byte. /usr/local/pike/7.9.5/lib/modules/_Charset.so:1: _Charset.UTF8dec()->feed("´") /usr/local/pike/7.9.5/lib/modules/Stdio.pmod/module.pmod:1815: Stdio.FILE("stdin", "r", 777 /* fd=0 */)->__lambda_66475_0_line_1814("´") /usr/local/pike/7.9.5/lib/modules/Stdio.pmod/module.pmod:1716: Stdio.FILE("stdin", "r", 777 /* fd=0 */)->low_get_data() /usr/local/pike/7.9.5/lib/modules/Stdio.pmod/module.pmod:2118: Stdio.FILE("stdin", "r", 777 /* fd=0 */)->read(1024,1) /usr/local/pike/7.9.5/lib/modules/Stdio.pmod/Readline.pike:582: Stdio.Readline()->InputController()->run_blocking() /usr/local/pike/7.9.5/lib/modules/Stdio.pmod/Readline.pike:1658: Stdio.Readline()->edit("",UNDEFINED,UNDEFINED) /usr/local/pike/7.9.5/lib/modules/Tools.pmod/Hilfe.pmod:2538: Tools.Hilfe.StdinHilfe()->create(UNDEFINED) /usr/local/pike/7.9.5/lib/modules/Tools.pmod/Hilfe.pmod:2474: Tools.Hilfe.StdinHilfe() Ignoring whatever is wrong with the terminal settings, where should this error be caught? It doesn't feel like something the user of the Readline object should have to care about, or is it?

1 0

sscanf bug?
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 08 Nov '12

08 Nov '12

Shouldn't I get ({ "0", "1" }) from this? > array_sscanf("01", "%[0]s%s"); (1) Result: ({ /* 1 element */ "0" })

2 2

Xenofarm
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 05 Nov '12

05 Nov '12

Your "cron" job on bahamut . .profile && ./client.sh >/dev/null produced the following output: --2012-11-04 17:24:00-- http://pike.ida.liu.se/generated/pikefarm/packages/7.8/latest Resolving pike.ida.liu.se... 130.236.254.72 Connecting to pike.ida.liu.se|130.236.254.72|:80... connected. HTTP request sent, awaiting response... 302 Temporary Relocation Location: http://pike.lysator.liu.se/generated/pikefarm/packages/7.8/latest [following] --2012-11-04 17:24:00-- http://pike.lysator.liu.se/generated/pikefarm/packages/7.8/latest Resolving pike.lysator.liu.se... 130.236.254.69, 2001:6b0:17:f0a0::45 Connecting to pike.lysator.liu.se|130.236.254.69|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2012-11-04 17:24:02 ERROR 404: Not Found.

2 1

7.6.132: new long term stable release
by H. William Welliver III 04 Nov '12

04 Nov '12

Good afternoon all, I've decided that 7.6.132 is stable enough on systems that have historically run 7.6 that it can be made the new official release on that long term stable branch. For anyone interested, the URL is: http://pike.ida.liu.se/download/pub/pike/all/7.6.132/ For platforms that contain a 7.6 package, it would be worthwhile to update those packages so that important bug fixes are available. There was some concern about bundles not working, and I think I have determined the reason. Some of the dependencies (bundled version of nettle, in particular, it seems) may not cope well with newer, more common ABIs and the linker wants to default to one nettle just doesn't like. A good example of this is 64-bit x86, so you may need to include appropriate "-arch i386" arguments in your LDFLAGS to force ld into 32 bit mode in addition to using "--with-abi=32". As always, please do let me know if there are any comments/concerns/questions about this new release. Best, Bill

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