Pike-devel October 2014

pike-devel@lists.lysator.liu.se

6 participants
28 discussions

Setting socket options: so many, uhh, options!
by Chris Angelico 10 Mar '15

10 Mar '15

Topic branch: rosuav/sockopt Per Lance's suggestion, I've made a generic setsockopt() function. It works only with integers, so it's not suitable for SO_LINGER, which therefore should stay the way it is (linger() takes a magic parameter of -1), but it works for any of the simple boolean options. As to shortcut functions, though, there are a few ways they can be done. 1) set_keepalive() always exists, even if SO_KEEPALIVE isn't available. If you call it when there's no SO_KEEPALIVE, it sets errno and returns failure. 2) set_nodelay() exists only if TCP_NODELAY is available. 3) setsockopt() itself is useless without the constants, and Stdio.TCP_NODELAY will exist only if TCP_NODELAY is available. So in a Pike script, using setsockopt() requires either has_index() run-time checks or #if compile-time checks for the options you want; set_keepalive's model works easily if you know that the Pike version you're targeting supports it; and set_nodelay's model lets you treat older Pikes and systems without that feature the same way. I'd rather make it as easy as possible on the Pike code. Which way makes more sense? ChrisA

5 13

xenofarm?
by Stephen R. van den Berg 03 Dec '14

03 Dec '14

Xenofarm seems to have been out of order since a while, correct? -- Stephen.

6 7

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

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

1 0

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

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 October 2014