Pike-devel January 2014

pike-devel@lists.lysator.liu.se

5 participants
12 discussions

negative indices in array ranges
by Martin Baehr 14 Aug '26

14 Aug '26

hi, instead of having to do: reverse(reverse(foo/"/")[1..]); i'd very much prefer: (foo/"/")[..-2]; are there any reasons that speak against supporting this other than me not being able to offer a patch? greetings, martin.

13 51

negative indices in array ranges
by Mirar ＠ Pike developers forum 14 Aug '26

14 Aug '26

levels might possibly be from -1 and up, -1 meaning infinite.

10 25

pike_frame->fun = FUNCTION_BUILTIN
by Arne Goedeke 16 Apr '26

16 Apr '26

In INIT, EXIT and some gc callbacks the fun in Pike_fp is set to FUNCTION_BUILTIN. there are some places in the code (e.g. ADT.List()->_get_iterator) where ->fun is used in INHERIT_FROM_INT et al, which segfaults (except with PIKE_DEBUG). I am not sure where to fix this. Should the *_FROM_INT macros check for FUNCTION_BUILTIN or is this better to be handled in the individual INIT/EXIT methods ? does anyone object to making ADT.Stack and ADT.Queue inherit ADT.List? arne

3 2

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

10 Apr '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) >

4 3

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

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 31 Oct '14

31 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

pike 7.8 alpha
by H. William Welliver III 24 Jan '14

24 Jan '14

I've uploaded a tentative "alpha" release, 7.8.808. Please feel free to download and comment. If everything looks good, I'll promote it to beta in a week or so (or will prepare a new alpha if things don't look so good). http://pike.lysator.liu.se/download/pub/pike/alpha/7.8.808/ Best, Bill

4 6

do crash pike
by Martin Bähr 15 Jan '14

15 Jan '14

hi, in pike 7.6 the following leads to a clean error: void do(){}; mixed ___HilfeWrapper() { return do; } crash.pike:1:do is a reserved word. crash.pike:2:do is a reserved word. crash.pike:2:syntax error, unexpected ';' Pike: Failed to compile script: Compilation failed. in 7.8 or 7.9 it leads to a fatal crash: pike79 crash.pike crash.pike:1:do is a reserved word. /local/users/mbaehr/src/pike/src/pike_types.c:677: Fatal error: Type mark stack underflow Backtrace at time of fatal: -:1: PikeCompiler("", UNDEFINED, -1, -1, target, UNDEFINED)->compile() -:1: DefaultCompilerEnvironment->compile(PikeCompiler("", UNDEFINED, -1, -1, target, UNDEFINED)) /usr/local/pike/7.9.5/lib/master.pike:1172: compile_string("void do(){}\nmixed ___HilfeWrapper() { return do; }\n","/local/users/mbaehr /home/src/pike/crash.pike",UNDEFINED,/local/users/mbaehr/home/src/pike/crash,0,UNDEFINED) /usr/local/pike/7.9.5/lib/master.pike:1896: master()->low_findprog("/local/users/mbaehr/home/src/pike/crash",".pike",UNDEFINED,UNDEFINE D) /usr/local/pike/7.9.5/lib/master.pike:2011: master()->findprog("/local/users/mbaehr/home/src/pike/crash",".pike",UNDEFINED,UNDEFINED) /usr/local/pike/7.9.5/lib/master.pike:2050: master()->low_cast_to_program("/local/users/mbaehr/home/src/pike/crash","/usr/local/pike/7. 9.5/lib/master.pike",UNDEFINED,UNDEFINED) /usr/local/pike/7.9.5/lib/master.pike:2084: master()->cast_to_program("/local/users/mbaehr/home/src/pike/crash.pike","/usr/local/pike/7 .9.5/lib/master.pike",UNDEFINED) fish: Job 2, “pike79 crash.pike ” terminated by signal SIGABRT (Abort) this works in different variations. void do() { mixed bar = ""; } or void do() {} mixed bar() { return ""; } trigger the same error, whereas void do(){} void do(){ write("bar"); } mixed do(){ return 1; } all work correctly greetings, martin.

2 1

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