Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Start a nNew thread

Pike 8.0 RC1
by Mirar ＠ Pike developers forum 28 Oct '14

28 Oct '14

Any new version that might work better around?

1 0

Pike 8.0 RC1
by Mirar ＠ Pike developers forum 25 Oct '14

25 Oct '14

Target system is a Razberry (pi with z-wave addon distribution).

1 0

Stdio.Buffer, need a way to revisit old positions in the output
by Stephen R. van den Berg 20 Oct '14

20 Oct '14

In perusing the Stdio.Buffer for pgsql NG, I find that I need some way to: a. Fill the output buffer. b. Leave a spot for say a 4 byte integer. c. Fill the output buffer some more. d. Revisit spot (b). e. Write out the newly calculated length. f. Return back to the current tip of the buffer. And all this has to work reliably even if during this, some part of the output buffer is already flushed to a filedescriptor (but not beyond the spot (b), the output code already takes care not to flush more than that). I was thinking something like: int Stdio.Buffer->getaddpos(); Stdio.Buffer->setaddpos(int oldpos); Whereas the numbers returned and used are only guaranteed to work as long as the underlying buffer has not been trimmed in the meantime. A typical sequence would then look like: Stdio.Buffer b=Stdio.Buffer(); int oldpos,endpos; b->add("abc"); b->add("d"); oldpos=b->getaddpos(); b->add_int32(0); /* or: b->setaddpos(oldpos+4); */ b->add("fghijklm"); /* This part is generated dynamically */ b->output_to(fd,3); /* Already outputs the initial abc */ endpos=b->getaddpos(); b->setaddpos(oldpos); b->add_int32(endpos-oldpos-4); b->setaddpos(endpos); b->output_to(fd); Any better ideas? -- Stephen.

2 1

Re: Freeze of Debian 8.0 "jessie"
by Chris Angelico 19 Oct '14

19 Oct '14

On Wed, Oct 15, 2014 at 1:00 AM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > What do we need to make a 8.0 release this week, even if it is only > for Debian? Possibly fix the docs building, which (last I checked) is failing in 8.1 and 8.0. ChrisA

3 3

Re: Text files
by Chris Angelico 19 Oct '14

19 Oct '14

On Mon, Oct 20, 2014 at 2:20 AM, Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > README-GIT : Should be verified. The autoconf section needs an update > on working versions. I'm having no trouble with autoconf 2.69, for instance. What versions are other people using? ChrisA

2 1

Text files
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 19 Oct '14

19 Oct '14

Some touch ups we may want to do. COMMITTERS : Update or delete this file? README : This could need some improvements. At least the BUGS section is not very usable. README-GIT : Should be verified. The autoconf section needs an update on working versions.

1 0

Stdio.Buffer->add() thread safe?
by Stephen R. van den Berg 17 Oct '14

17 Oct '14

Would it be feasible/prudent/costly to make Stdio.Buffer->add() thread safe? I have the practical problem that I need to append to a buffer from different threads. The alternative is to use a Thread.Queue. -- Stephen.

2 1

Stdio.Buffer->add() thread safe?
by Per Hedbor () ＠ Pike (-) developers forum 17 Oct '14

17 Oct '14

> It is thread safe. In fact, all buffer methods are. With one exception: If you have a buffer-is-empty handler function, that function has to be threadsafe for the buffer object to be so. -- Per Hedbor

1 0

Bad offset: pc program
by Stephen R. van den Berg 17 Oct '14

17 Oct '14

Pike 8.1 on amd64 with machine code, with double floats. Trying some heavy threading/muxing/locking/callbacks for a new and improved pgsql driver, I get this (consistently reproducible): Bad offset: pc:0x7f92405be36c program:0x7f92408df050 (0x36e0) Which doesn't seem right. Anything obvious I can do to help pinpoint this? -- Stephen.

1 0

_Roxen.http_decode_string
by Arne Goedeke 16 Oct '14

16 Oct '14

overflows the string if it encounters a truncated sequence, e.g. a trailing % or %u with less than 4 hex chars. The testsuite seems to assume that these are legal inputs. I would like to add some overflow checks and errors, instead of decoding uninitialized memory or segfaulting. There are also no checks if the sequences are valid hex values, maybe that should also be caught? arne

2 2

Jump to page:

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