Pike-devel January 2026

pike-devel@lists.lysator.liu.se

3 participants
3 discussions

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 20 Jan '26

20 Jan '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)?

4 3

Protocols.HTTP.Query and 100 Continue
by H. William Welliver 14 Jan '26

14 Jan '26

Hello all, I found myself interacting with a HTTP server that returns 100 Continue responses to HTTP POST requests. The pike HTTP client treats those as the final response, but they’re are meant to be considered intermediate responses. I couldn’t figure out if there was a way to get it to continue past that, and it doesn’t look like there is. The standard says a server shouldn’t send them if they aren’t requested, but also says that clients must treat them as informational and carry on. I have a proposed fix, but since that’s a messing with a pretty widely used bit of code, I wanted to get feedback before I start making changes. I don’t know if there are other similar scenarios that this fix doesn’t cover; I’d be happy to hear feedback on that as well. In Protocols.pmod/HTTP.pmod/Query.pike, following this line: int bytes_read = sscanf(headerbuf,"%s%*[ ]%d%*[ ]%s%*[\r]",protocol,status,status_desc); add: // we don't expect continue responses, but we must deal with them, // and treat them as informational if(status == 100) { int q = sizeof(headerbuf); // find the end of the response message, and move past the newlines present. // since the whole request has been sent already, we just have to wait for the response, // if it isn’t already in the buffer. Either way, there should be trailing line endings, // as those were required to be present for us to have gotten this far. while(q < sizeof(buf)) { if(buf[q] == '\n' || buf[q] == 'r') continue; break; } // reset the buffer to the point just past the continue response and start over. buf = buf[q+1..]; // a better approach might be a do-while loop, but this is a bit clearer, // and we shouldn't find ourselves recursing more than once. return ponder_answer(); } I think this affects all versions of pike (certainly 8.x and 9.x). Thanks in advance! Bill

1 0

Generated (precompiled) function names changing
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 08 Jan '26

08 Jan '26

When building both the current stable 8.0 and 9.0.11, *sometimes* the C code gets regenerated from .cmod (by precompile.pike, I guess) and then the macros in src/modules/Gmp/mpq.c change names from f_mpq_* to f_Gmp_mpq_* (and similarly in other modules), which in that case causes compilation to fail because mpq.cmod contains references to some of the generated function names, e.g. f_mpq_get_int(0) in cast(string). Any idea how this is happening and if it's supposed to happen and the function calls should be changed to match?

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