Pike-devel February 2016

pike-devel@lists.lysator.liu.se

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

Re: Setting socket options: so many, uhh, options!
by Chris Angelico 15 Sep '16

15 Sep '16

On Tue, Mar 10, 2015 at 10:05 PM, Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Wait, I said REUSEPORT? What's the difference to REUSEADDR? Mysteries > of TCP sockets... Here's a decent explanation, I think: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and… ChrisA

3 6

Pike 8.0.182 release candidate
by Peter Bortas 10 Mar '16

10 Mar '16

Release candidate for testing: https://pike.lysator.liu.se/pub/pike/beta/8.0.182/Pike-v8.0.182.tar.gz Changes since Pike 8.0.164 (current stable) ---------------------------------------------------------------------- New features ------------ o gc It is now possible to run the gc in a quick mode to just cut weak references from a specific container. Bug fixes --------- o ADT.Heap The Element class lost track of its position when remove() was used. o Filesystem.Monitor * Improved thread safety and robustness * Inotify-related fixes. o pgsql The new driver in 8.0 suffered from filedescriptor leaks if the database connections were not explicitly close()d. Fixes have been applied which eliminate the filedescriptor leak and also ensure that the filedescriptors are closed the instant the object loses all references. o programs The runtime now attempts to wait for any compilations in progress to complete before complaining about cloning of unfinished programs. This fixes a race-condition when the same program is compiled from different threads. o Runtime Fixed multiple potential NULL-dereferences. o SSL.File Fixed breaking of circular references when the peer terminates the connection. o Standards.URI Support the userinfo field containing '@'. o Stdio.File The second argument to set_buffer() should now work. o Testsuite Updated the SHA3_* testvectors to FIPS 202. Building and installing ----------------------- o Multiple fixes for building on Solaris 11.

4 6

Pike 8.0 rel 2 this weekend
by Peter Bortas ＠ Pike developers forum 28 Feb '16

28 Feb '16

As earlier announced I will build an RC for the second release of Pike 8.0 this weekend, and if all goes well release it on Tuesday. If you are sitting on some low risk fix patch now is the time to check it in. -- Peter Bortas

2 1

IA64
by Peter Bortas ＠ Pike developers forum 15 Feb '16

15 Feb '16

Removing silencing of warnings is fine, but I don't want IA64 specific runtime-support to be removed if there is any.

1 0

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 February 2016