Pike-devel April 2017

pike-devel@lists.lysator.liu.se

2 participants
8 discussions

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

GTK/GDK on OSX
by H William Wellliver III 08 Jan '18

08 Jan '18

I’m running into some build problems on OSX. It seems that the GTK module assumes that if a system is NT that gdkwin.h is used and otherwise gdkx.h is used. Unfortunately, it seems that on some builds of GTK/GDK for OS X, neither of those is correct and that gdkquartz.h should be used. I’m guessing that some configure tests are needed to determine which of the 3 files is actually present. However a quick look at configure.in leaves me unsure how best to include that. Anyone with more expertise in the GTK module’s inner workings care to weigh in? Bill

4 9

Proposal: Create Stdio.Port from systemd-provided socket
by Chris Angelico 23 Nov '17

23 Nov '17

Branch: rosuav/systemd-sockets Currently, you can create a Stdio.Port("stdin") as a means of accepting a socket handed to you as FD 0. However, there's no way to accept a socket given as any other FD, making it impossible to use this for systemd's sockets. Example: $ cat /etc/systemd/system/listendemo.service [Unit] Description=Listen Demo Requires=listendemo.socket [Service] User=rosuav ExecStart=/usr/local/bin/pike /home/rosuav/listendemo.pike WorkingDirectory=/home/rosuav $ cat /etc/systemd/system/listendemo.socket [Socket] ListenStream=123 $ cat listendemo.pike object mainsock = Stdio.Port("systemd", acceptloop); void acceptloop() { while (object sock=mainsock->accept()) { write("Accepted sock: %O\n", sock); sock->write("Stub\n"); sock->close(); } } int main() { write("Main sock: %O\n", mainsock); return -1; } Note that the "User=rosuav" directive means that Pike is run as a non-root user. This spares the application the hassle of managing privileges securely, as it never gets root privileges (assuming, of course, that the only reason it needed root was to bind to a privileged port, which is true for a lot of programs). As with "stdin" mode, the second parameter is optional (blocking vs nonblocking). This won't break on non-systemd systems for two reasons: firstly, all it ever does is query environment variables, and secondly, it does this only if the application requests it explicitly, so you have to actually ask for it. Is this something that would be useful? Feel free to bikeshed the API - it's not in 8.1 yet, so anything can change. ChrisA

3 6

Bad function identifier on 8.1
by Stephen R. van den Berg 30 May '17

30 May '17

While trying to use Pike 8.1, I consistently get the following on stderr whenever I run pike: /usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod.o:-: Warning: Decode failed: Error while decoding program(/usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod:23): Bad function identifier offset for random_string:function(int(0..2147483647) : string(8bit)): 3 != 0 It's not immediately obvious to me how to fix this. Anyone? Or am I the only one seeing this? -- Stephen.

2 4

pike compile failes on fedora 25 x86_64
by josef radinger 22 May '17

22 May '17

hi i try to compile pike for fedora 25 and it fails as below: ... precompile: /usr/local/bin/pike80 /tmp/Pike- v8.0.404/bin/precompile.pike --base=FSEvents /tmp/Pike- v8.0.404/src/modules/FSEvents/fsevents.cmod (method=QQQQQQ) Compiling modules/FSEvents/fsevents.c Linking FSEvents #### Making dynamic: modules/Fuse Compiling modules/Fuse/fuse.c Linking Fuse Making module.pmod #### Making dynamic: modules/Gdbm Compiling modules/Gdbm/gdbmmod.c /tmp/Pike-v8.0.404/src/pike_error.h:54:34: error: expected ‘)’ before string constant (fprintf(stderr,msg_fatal_error,__FILE__,(long)__LINE__),debug_fatal) ^ In file included from /tmp/Pike-v8.0.404/src/threads.h:11:0, from /tmp/Pike-v8.0.404/src/modules/Gdbm/gdbmmod.c:9: /tmp/Pike-v8.0.404/src/pike_error.h:54:58: error: expected ‘)’ before ‘,’ token (fprintf(stderr,msg_fatal_error,__FILE__,(long)__LINE__),debug_fatal) ^ Compilation command was: /tmp/Pike-v8.0.404/build/linux-4.10.8-200.fc25.x86_64-x86_64/smartlink gcc -I. -I/tmp/Pike-v8.0.404/src/modules/Gdbm -I/tmp/Pike- v8.0.404/build/linux-4.10.8-200.fc25.x86_64-x86_64 -I/tmp/Pike- v8.0.404/src -I/usr/local/include -DHAVE_CONFIG_H -g -ggdb -m64 - mrdrnd -fvisibility=hidden -O3 -pipe -fvar-tracking-assignments -funswitch-loops -W -Wall -Wno-unused -Wcomment -Wformat -Wimplicit- function-declaration -Wmultichar -Wunused-function -Wswitch -Wuninitialized -Wpointer-arith -Wchar-subscripts -Wno-long-long -Wdeclaration-after-statement -fPIC -DDYNAMIC_MODULE -c /tmp/Pike- v8.0.404/src/modules/Gdbm/gdbmmod.c -o gdbmmod.o Makefile:167: recipe for target 'gdbmmod.o' failed make[6]: *** [gdbmmod.o] Error 1 Makefile:100: recipe for target 'all' failed make[5]: *** [all] Error 2 Makefile:100: recipe for target 'Gdbm' failed make[4]: *** [Gdbm] Error 1 Makefile:1175: recipe for target 'dynamic_module_objects' failed make[3]: *** [dynamic_module_objects] Error 1 Makefile:1195: recipe for target 'module_objects' failed make[2]: *** [module_objects] Error 2 Makefile:149: recipe for target '_make_in_builddir' failed make[1]: *** [_make_in_builddir] Error 2 Makefile:66: recipe for target 'compile' failed make: *** [compile] Error 2

2 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 April 2017