Pike-devel May 2013

pike-devel@lists.lysator.liu.se

5 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 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

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

FYI/RFC: Variant functions in Pike 7.9
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 27 May '13

27 May '13

FYI: The support for variant function (aka polymorphic overloading) has now reached a semi-useable state in Pike 7.9: | Pike v7.9 release 5 running Hilfe v3.5 (Incremental Pike Frontend) | > class foo { | >> variant int bar(int a) { return a*2; } | >> variant string bar(string s) { return "FOO" + s + "FOO"; } | >> variant string bar() { return "FOO"; } | >> } | > typeof(foo()->bar); | (1) Result: function( : string) | function(int : int) | function(string : string) | > foo()->bar(17); | (2) Result: 34 | > foo()->bar("BAR"); | (3) Result: "FOOBARFOO" | > foo()->bar(); | (4) Result: "FOO" | > foo()->bar(1.2); | Compiler Error: 1: Bad argument 1 to bar. | Compiler Error: 1: Expected: string | int. | Compiler Error: 1: Got : float. | > foo()->bar((mixed)1.2); | Invalid arguments to bar()! | HilfeInput:1: HilfeInput()->foo()->bar(1.2) | HilfeInput:1: HilfeInput()->___HilfeWrapper() I would appreciate feedback especially regarding the expected semantics for: * When the variants have different modifiers (protected, private, etc). * When there's a function without the variant keyword. * When the types for the variants aren't disjunct. * When overriding X from an inherit with a variant function. - A non-variant function. - A variant function with a new definition with the same type. - A variant function with a new definition with a different type. * Should the previous definition be accessible in any of the above cases, or only if there's an explicit trampoline? * Multiple inherits of variant functions. - With the same types. - With different types. I've probably forgotten or not thought of some cases, please mention the expected semantics for these as well. /grubba

4 4

Fwd: Bug#708366: pike7.8: FTBFS due to conflicting REG_* definitions
by Magnus Holmgren 26 May '13

26 May '13

OK, so now all of REG_EAX, REG_EBX and so on are defined on Linux, or rather, in the newest eglibc. Do you prefer renaming the enum items or #undef-ing all of them? ---------- Forwarded message ---------- Subject: Bug#708366: pike7.8: FTBFS due to conflicting REG_* definitions Date: onsdagen den 15 maj 2013 From: Colin Watson <cjwatson(a)ubuntu.com> To: submit(a)bugs.debian.org Package: pike7.8 Version: 7.8.700-2 Severity: serious User: ubuntu-devel(a)lists.ubuntu.com Usertags: origin-ubuntu saucy pike7.8 fails to build in unstable as follows: Compiling pikecode.c In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0: /«PKGBUILDDIR»/src/code/ia32.c:22:16: error: redeclaration of enumerator 'REG_EAX' In file included from /usr/include/signal.h:360:0, from /usr/include/i386-linux-gnu/sys/param.h:28, from /«PKGBUILDDIR»/src/pike_macros.h:14, from /«PKGBUILDDIR»/src/program.h:12, from /«PKGBUILDDIR»/src/pikecode.c:15: /usr/include/i386-linux-gnu/sys/ucontext.h:180:3: note: previous definition of 'REG_EAX' was here In file included from /«PKGBUILDDIR»/src/pikecode.c:25:0: /«PKGBUILDDIR»/src/code/ia32.c:22:29: error: redeclaration of enumerator 'REG_EBX' In file included from /usr/include/signal.h:360:0, from /usr/include/i386-linux-gnu/sys/param.h:28, from /«PKGBUILDDIR»/src/pike_macros.h:14, from /«PKGBUILDDIR»/src/program.h:12, from /«PKGBUILDDIR»/src/pikecode.c:15: /usr/include/i386-linux-gnu/sys/ucontext.h:174:3: note: previous definition of 'REG_EBX' was here *snip* It looks painful to reliably avoid the enumeration values in <sys/ucontext.h>. I suggest simply renaming Pike's enumeration values. Thanks, -- Colin Watson [cjwatson(a)ubuntu.com] ------------------------------------------------------- -- Magnus Holmgren holmgren(a)debian.org Debian Developer

2 2

callback support for encoding JSON
by Martin Bähr 24 May '13

24 May '13

hi, the JSON module can only encode objects if they provide an encode_json function. i find this a bit limiting because it is hardly possible to add encode_json to all classes that would need it. better would be to allow the caller of JSON.encode provide a callback for objects that the module can't handle by itself. it seems to me the simplest would be to add an argument to JSON.encode to allow passing a function. and then call that function of the object has none of its own. i am unfamiliar with CMODs but i think in src/post_modules/JSON/json.cmod i need to add the function to the encode_context and then call it in the PIKE_T_OBJECT case. also what i am wondering is, should i store the whole svalue for the function or just the functionpointer itself? (is that u.efun->function?) greetings, martin.

5 19

Segfaults and module dumping failures starting in acab7b82dc
by H. William Welliver III 22 May '13

22 May '13

I've noticed that installs of 7.9 after commit acab7b82dc have started generating a large number of module dumping failures. Also, I have code that segfaults on startup starting with the same commit. The code is somewhat complicated, so I've not been able to boil it down to a simple test (yet). I'm not sure the gdb backtrace will be of much help, but I'll include it here. Any suggestions? Bill Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000180 [Switching to process 19605 thread 0x1803] 0x000000010017f8a5 in insert_opcode1 () (gdb) bt #0 0x000000010017f8a5 in insert_opcode1 () #1 0x0000000100067fd7 in do_docode2 () #2 0x000000010006be4f in do_docode2 () #3 0x00000001000710a2 in do_cond_jump () #4 0x0000000100071002 in do_cond_jump () #5 0x000000010006ecae in do_docode2 () #6 0x000000010006854d in do_docode2 () #7 0x0000000100070a24 in do_code_block () #8 0x000000010016331a in dooptcode () #9 0x000000010000b0eb in yyparse () #10 0x0000000100107a76 in run_pass2 () #11 0x000000010010b5da in f_compilation_compile () #12 0x0000000100018235 in low_mega_apply () #13 0x0000000100019684 in mega_apply () #14 0x00000001000efe76 in f_compilation_env_compile () #15 0x0000000100018235 in low_mega_apply () #16 0x0000000100019684 in mega_apply () #17 0x0000000101181f6e in ?? () #18 0x000000010000f736 in catching_eval_instruction () #19 0x000000010001caeb in inter_return_opcode_F_CATCH () #20 0x000000010118b425 in ?? () #21 0x000000010001969f in mega_apply () #22 0x00000001000dca1d in object_index_no_free () #23 0x00000001007e2dcc in ?? () #24 0x000000010001969f in mega_apply () #25 0x00000001000dca1d in object_index_no_free () #26 0x00000001000eb3bc in f_index () #27 0x00000001001590cf in index_node () #28 0x000000010000a561 in yyparse () #29 0x000000010010b4f1 in f_compilation_compile () #30 0x0000000100018235 in low_mega_apply () #31 0x0000000100019684 in mega_apply () #32 0x00000001000efe76 in f_compilation_env_compile () #33 0x0000000100018235 in low_mega_apply () #34 0x0000000100019684 in mega_apply () #35 0x0000000101181f6e in ?? () #36 0x000000010000f736 in catching_eval_instruction () #37 0x000000010001caeb in inter_return_opcode_F_CATCH () #38 0x000000010118b425 in ?? () #39 0x000000010001969f in mega_apply () #40 0x00000001000dca1d in object_index_no_free () #41 0x00000001007e2dcc in ?? () #42 0x000000010001969f in mega_apply () #43 0x00000001000dca1d in object_index_no_free () #44 0x00000001000eb3bc in f_index () #45 0x00000001001590cf in index_node () #46 0x000000010000a561 in yyparse () #47 0x000000010010b4f1 in f_compilation_compile () #48 0x0000000100018235 in low_mega_apply () #49 0x0000000100019684 in mega_apply () #50 0x00000001000efe76 in f_compilation_env_compile () #51 0x0000000100018235 in low_mega_apply () #52 0x0000000100019684 in mega_apply () #53 0x0000000101181f6e in ?? () #54 0x000000010000f736 in catching_eval_instruction () #55 0x000000010001caeb in inter_return_opcode_F_CATCH () #56 0x000000010118b425 in ?? () #57 0x000000010001969f in mega_apply () #58 0x00000001000dca1d in object_index_no_free () #59 0x00000001007e2dcc in ?? () #60 0x000000010001969f in mega_apply () #61 0x00000001000dca1d in object_index_no_free () #62 0x00000001000eb3bc in f_index () #63 0x00000001001590cf in index_node () #64 0x000000010000a561 in yyparse () #65 0x000000010010b4f1 in f_compilation_compile () #66 0x0000000100018235 in low_mega_apply () #67 0x0000000100019684 in mega_apply () #68 0x00000001000efe76 in f_compilation_env_compile () #69 0x0000000100018235 in low_mega_apply () #70 0x0000000100019684 in mega_apply () #71 0x0000000101181f6e in ?? () #72 0x000000010000f736 in catching_eval_instruction () #73 0x000000010001caeb in inter_return_opcode_F_CATCH () #74 0x000000010118b425 in ?? () #75 0x000000010001969f in mega_apply () #76 0x00000001000e4517 in o_cast () #77 0x00000001000e4c2c in f_cast () #78 0x00000001049abfe1 in ?? () #79 0x000000010001969f in mega_apply () #80 0x00000001000d5db8 in call_pike_initializers () #81 0x00000001000d992c in debug_clone_object () #82 0x00000001000182fc in low_mega_apply () #83 0x000000010001bda4 in jump_opcode_F_CALL_FUNCTION () #84 0x0000000101e3f4d4 in ?? () #85 0x000000010000f736 in catching_eval_instruction () #86 0x000000010001caeb in inter_return_opcode_F_CATCH () #87 0x0000000101e3f179 in ?? () #88 0x000000010001969f in mega_apply () #89 0x000000010012e5a0 in new_thread_func () #90 0x00007fff8d1af742 in _pthread_start () #91 0x00007fff8d19c181 in thread_start ()

1 0

segfault when building pike 7.8 on olpc/fedora 18
by Martin Bähr 19 May '13

19 May '13

hi, i am getting a strange segfault after building pike: pike itself seems to build but it doesn't run. when i remove shuffler, then the build completes, but the same error comes back when i try make install. #### Making dynamic: post_modules/Shuffler [29/1915] /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/local/users/mbaehr/home/src/Pike-v7.8.700/bui ld/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i686/master.pike /local/users/mbaehr/home/src/Pi ke-v7.8.700/src/post_modules/Shuffler/make_sources.pike /local/users/mbaehr/home/src/Pike-v7.8.70 0/src/post_modules/Shuffler sources.h sources_to_compile /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:42: Error in constant definition. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:187: Failed to index module Files with 'Stat'. (Module doesn't exist?) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:368: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:368: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:376: No inherit or surrounding class Pike_0_5_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:411: No inherit or surrounding class Pike_0_5_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:438: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:438: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:649: No inherit or surrounding class Pike_0_6_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:673: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:673: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:712: No inherit or surrounding class Pike_7_0_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:736: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:736: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:806: No inherit or surrounding class Pike_7_2_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:830: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:830: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:864: No inherit or surrounding class Pike_7_4_master. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:881: Cannot inherit program in pass 1 which is only a placeholder. /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:881: (You probably have a cyclic symbol dependency that the compiler cannot handle. ) /local/users/mbaehr/home/src/Pike-v7.8.700/build/linux-3.3.8_xo1.5-20130315.1502.olpc.4fc7bc3-i68 6/master.pike:1490: Error in constant definition. make[4]: *** [override] Segmentation fault make[3]: *** [Shuffler] Error 1 make[2]: *** [post_module_objects] Error 1 make[1]: *** [_make_in_builddir] Error 2 make: *** [compile] Error 2 greetings, martin. -- eKita - the online platform for your entire academic life hackerspace beijing - http://societyserver.org/hackerspace-beijing/ -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net foresight developer realss.com foresightlinux.org unix sysadmin trainer developer societyserver.org Martin Bähr working in china http://societyserver.org/mbaehr/

2 4

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 May 2013