Pike-devel March 2017

pike-devel@lists.lysator.liu.se

5 participants
5 discussions

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

Faster calls (again)
by Arne Goedeke 21 Mar '17

21 Mar '17

Ok, not sure yet if this is going anywhere this time, but I decided to attempt a second time to refactor the current function call code into something which is more readable, more flexible and hopefully faster (at some point). The branch is called 'arne/faster_calls_again'. The API is similar to what the previous version did, the main difference being that it allocates pike frames only if needed (not for efuns, casts, apply_array, etc). The changes in that branch start by first removing code which was duplicated at some point to increase performance for certain types of calls. I then added a series of new functions to initialize, execute and deinitialize a callsite. Then, I started to use it in some of the existing function call APIs and also implemented that optimized version of f_map. The code is probably broken in interesting ways, I have not tested it very well, yet. It compiles and installs. Otherwise on my list right now: * cleanup * reduce API granularity somewhat * re-add tracing and dtrace code (could all be in one place now) * optimize automap * try to optimize apply_array (e.g. when calling the same function in different instances of the same class) * make tail recursion not allocate a new frame, instead just re-use the current one Feedback and help welcome, Arne

3 8

need access to upload pike binary
by H William Wellliver III 18 Mar '17

18 Mar '17

Hi, I've finally had some time to get a proper build environment for MacOS X and have a Pike binary built that contains no external dependencies. However, I don't seem to have access any more to upload the file as I used to (previously I had ssh access to what was called at one time pelix). Can someone contact me privately to let me know how best to get the file uploaded? Thanks in advance! Bill

1 0

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 March 2017