Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

Re: Autodoc 8.1 complains about removed namespaces
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 20 Nov '14

20 Nov '14

> >Well, I merely tied up the loose ends that were a natural result of >all compat support prior to 7.8 being ripped out already (not by me). >I.e. the functionality that *I* removed was already dead-in-the-water because >there was no way to call it anymore. > No, you could still call them. I kept them in because just because it was compatibility with old data, not old code.

3 2

crash
by Arne Goedeke 12 Nov '14

12 Nov '14

I attached a simple script which crashes pike. The code has cyclic dependencies within the same pmod, and ends up having parent_identifier=-1 in find_external_context. When compiled with debug, running pike -M lib test.pike results in the following backtrace. /home/el/code/rw/pike/src/interpret.c:778: Fatal error: Identifier out of range, loc->parent_identifer=-1! Backtrace at time of fatal: lib/Test.pmod/FOO.pmod:8: Test.A()->__INIT() lib/Test.pmod/module.pmod:5: Test.A()->__INIT() test.pike:3: /main()->main(1,({"/home/el/code/rw/pike_bugs/1/test.pike"})) Aborted Arne

1 0

cannot find input file: `wnotify_config.h.in'
by Stephen R. van den Berg 04 Nov '14

04 Nov '14

Compiling 8.1 on i386 stops at: configure: creating ./config.status config.status: creating make_variables config.status: creating Makefile config.status: error: cannot find input file: `wnotify_config.h.in' Any ideas? -- Stephen.

3 5

Re: Proposal: Enhance Process.run() to accept functions for stdout/stderr
by Chris Angelico 03 Nov '14

03 Nov '14

On Tue, Nov 4, 2014 at 1:25 AM, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > I'd prefer you didn't. Supposed to be stable and all... No probs. All sorted then. ChrisA

2 1

Re: Proposal: Enhance Process.run() to accept functions for stdout/stderr
by Chris Angelico 03 Nov '14

03 Nov '14

On Mon, Nov 3, 2014 at 10:55 PM, Per Hedbor () @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>Any views on this feature? (I just rebased the branch on top of >>current 8.1, no other changes.) Fears of breakage? Interest in using >>it? Anything? > > It looks good to me. And, yes, it is worth adding since it is > something you often want. Cool. Merged into 8.1. Should I put it into 8.0 as well? ChrisA

2 1

Proposal: Enhance Process.run() to accept functions for stdout/stderr
by Chris Angelico 03 Nov '14

03 Nov '14

I periodically find myself needing something similar to Process.run(), but processing intermediate output. Example: https://github.com/Rosuav/FrozenOST/blob/master/build.pike#L114 It needs to take whatever's sent to stderr, turn all \n into \r, and send it on to the real stdout. (Yes, it sends stderr to stdout.) I usually end up lifting the code of Process.run() and making a cut-down version (as I don't need all its features); but the obvious alternative would be to have Process.run itself provide this facility. The code is now at branch rosuav/process_run_with_func; the equivalent to my above code would be simply: Process.run(({"sox","-S","-m","-v",".5"})+tracklist/1*({"-v",".5"})+({soundtrack}), (["stderr":lambda(string data) {write(replace(data,"\n","\r"));}])); Is this a feature worth adding? ChrisA

2 2

debugger opcodes
by Bill Welliver 30 Oct '14

30 Oct '14

I noticed that folks have been working on code generation lately. Any chance it might be possible to implement some of the opcodes required to get debugging working (step, break, etc)? I seem to recall someone indicating it wasn't a terribly difficult task, but it's clearly beyond my understanding of the problem. Bill

4 6

Re: Are there Sql backends that return an array from big_query()?
by H. William Welliver III 30 Oct '14

30 Oct '14

True, but the code that handles that case isn't very complex, so why create a potential compat problem? What's the benefit? Bill > On Oct 30, 2014, at 6:25 AM, Stephen R. van den Berg <srb(a)cuci.nl> wrote: > > But the official one doesn't do that anymore, I think. > > Just trying to chart how many of the builtin backends actually still need the Sql.sql_array_result. And if so, they should need to wrap it themselves by providing a big_query which already returns the wrapped version instead of relying on the Sql glue to fix it afterward. > >> On Thu, Oct 30, 2014 at 3:40 AM, H. William Welliver III <bill(a)welliver.org> wrote: >> I wrote a backend for SQLite (back before the official one existed) that did this; actually it retrieved the result as an array and then created a Sql.sql_array_result object with it as the argument to create(). I suspect that’s similar to what the code you refer to is doing. >> >> Bill >> >> > On Oct 29, 2014, at 10:05 PM, Stephen R. van den Berg <srb(a)cuci.nl> wrote: >> > >> > Looking at ways to streamline the Sql.Sql interface, I find that >> > there is code in the current big_query() to handle the case when >> > the return value of the real sql backend big_query() happens to be >> > an array instead of a genuine object, it puts a wrapper function around it. >> > >> > Are there currently any SQL backends which actually return an array from >> > big_query()? >> > -- >> > Stephen. > > > > -- > Stephen.

2 1

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

28 Oct '14

Except that quirk, it built fine on a Pi.

1 0

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

28 Oct '14

Not in src, but: $ find -name *0101* ./build/linux-3.12.22+-armv6l/0101010185

1 0

Jump to page:

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