Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

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

Pike 8.0 RC1
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 28 Oct '14

28 Oct '14

(See if a file called "0101010185" has been created in src/.)

1 0

Pike 8.0 RC1
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 28 Oct '14

28 Oct '14

It seems to be related to the issue I reported on 3 August: The touch command on line 1360 (as of then) of src/Makefile.in uses an obsolete syntax. Try this: --- a/src/Makefile.in +++ b/src/Makefile.in @@ -1357,7 +1357,7 @@ precompile.sh: $(SRCDIR)/precompile.sh.i # recursive use of make. precompile.sh-stamp: @if [ -f precompile.sh ]; then :; else $(MAKE) precompile.sh; fi - @touch 0101010185 precompile.sh-stamp 2>/dev/null + @touch -t 198501010101 precompile.sh-stamp 2>/dev/null $(SRCDIR)/machine.h.in: $(SRCDIR)/stamp-h.in @if test -f $(SRCDIR)/machine.h.in; then :; else \

1 0

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

28 Oct '14

That seems to be the problem.

1 0

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

28 Oct '14

$(SRCDIR)/interpret_functions_fixed.h: $(SRCDIR)/interpret_functions.h precompile.sh-stamp ./precompile.sh --cache make_interpret_functions.pike >"$@" "$(SRCDIR)/interpret_functions.h" || { rm "$@"; exit 1; } maybe precompile-sh.stamp isn't in the archive?

1 0

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

28 Oct '14

It immediately starts with: | $ make 2>&1 | tee makelog2 | | Configure arguments: | Use `make CONFIGUREARGS="..." ...' to change them. | They will be retained in the build directory. | | Making all in build/linux-3.12.22+-armv6l | ./precompile.sh --cache make_interpret_functions.pike >"/home/pi/Pike-v8.0.10/src/interpret_functions_fixed.h" "/home/pi/Pike-v8.0.10/src/interpret_functions.h" || { rm "/home/pi/Pike-v8.0.10/src/interpret_functions_fixed.h"; exit 1; } | /bin/sh: 1: cannot create /home/pi/Pike-v8.0.10/src/interpret_functions_fixed.h: Permission denied | rm: remove write-protected regular file `/home/pi/Pike-v8.0.10/src/interpret_functions_fixed.h'? (I put chattr +i on it.)

1 0

Pike 8.0 RC1
by Per Hedbor () ＠ Pike (-) developers forum 28 Oct '14

28 Oct '14

> Any new version that might work better around? Not really, no. The thing is, the files seems to have correct timestamps, so there should be no need to re-generate the interpret_functions file. Î© leopard$ ls -l interpret_functions* 91 -rw-rw-r-- 1 per per 92635 okt 20 15:51 interpret_functions_fixed.h 89 -rw-rw-r-- 1 per per 90090 okt 20 14:44 interpret_functions.h I really have no idea why it is regenerating them. :( -- Per Hedbor

1 0

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