Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Pike 8.0.254 beta/release candidate
by Peter Bortas 07 Jun '16

07 Jun '16

Pike 8.0.254 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.254/Pike-v8.0.254.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.254/Pike-v8.0.254-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.254/Pike-v8.0.254-win32-oldli… SSL certificates where fixed up after last release, so if anyone gets any warnings there let me know. On the positive side I have found my big box of Windows licenses. On the negative side Windows Update must be some kind of anti-pattern for running in VMs. They have been installing updates for 3 days now, and are not finished yet. So no attempt at newer build environment quite yet. Changes since Pike 8.0.240 (release 3) ---------------------------------------------------------------------- New features ------------ o Protocols.WebSocket Added client mode. o _Roxen.HeaderParser feed() can now be forced not to normalize (ie lower_case) the header names. Bug fixes --------- o Documentation Fixed some AutoDoc markup typos. o Fixed assertion failure in multiset handling. Indexing of non-empty multisets containing no objects or functions, with an object implementing lfun::`<() et al could cause assertion failures. o Filesystem.Monitor Fixed potential recursive mutex locks on destroy(). -- Peter Bortas

1 0

June Pike release Tuesday after this weekend
by Peter Bortas ＠ Pike developers forum 03 Jun '16

03 Jun '16

As usual there will be an attempt at Pike stable release the first Tuesday of the month. Please update the CHANGELOG with your bugfixes before Sunday lunch so we get them in the RC. /Peter Bortas

1 0

Error building 8.1: test-pike not found
by Pontus Östlund 27 May '16

27 May '16

Hi guys! When I try to build Pike 8.1 from Git I get an error saying pike-test is not found. What’s that about? Making all in build/linux-4.4.0-22-generic-x86_64 ./precompile.sh --cache precompile.pike --api=3 >"/home/poppa/src/pike-git/devel/src/builtin.c" "/home/poppa/src/pike-git/devel/src/builtin.cmod" || { rm "/home/poppa/src/pike-git/devel/src/builtin.c"; exit 1; } precompile: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/master.pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=Q) ./precompile.sh: 135: ./precompile.sh: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/pike: not found precompile: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/tpike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/master.pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=QQ) ./precompile.sh: 135: ./precompile.sh: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/tpike: not found precompile: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/test-pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=QQQ) ./precompile.sh: 135: ./precompile.sh: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/test-pike: not found precompile: pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=QQQQQQ) /home/poppa/src/pike-git/devel/src/builtin.cmod:2091: Syntax error: string(8bit) is not a valid type. precompile: /usr/local/bin/pike80 /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=QQQQQQ) /home/poppa/src/pike-git/devel/src/builtin.cmod:2091: Syntax error: string(8bit) is not a valid type. precompile: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/master.pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=Q) ./precompile.sh: 135: ./precompile.sh: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/pike: not found precompile: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/tpike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/master.pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=QQ) ./precompile.sh: 135: ./precompile.sh: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/tpike: not found precompile: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/test-pike /home/poppa/src/pike-git/devel/bin/precompile.pike --api=3 /home/poppa/src/pike-git/devel/src/builtin.cmod (method=QQQ) ./precompile.sh: 135: ./precompile.sh: /home/poppa/src/pike-git/devel/build/linux-4.4.0-22-generic-x86_64/test-pike: not found Failed to find a Pike executable that could run /home/poppa/src/pike-git/devel/bin/precompile.pike. Makefile:512: receptet för målet ”/home/poppa/src/pike-git/devel/src/builtin.c” misslyckades make[3]: *** [/home/poppa/src/pike-git/devel/src/builtin.c] Fel 1 Makefile:1156: receptet för målet ”module_objects” misslyckades make[2]: *** [module_objects] Fel 2 Makefile:149: receptet för målet ”_make_in_builddir” misslyckades make[1]: *** [_make_in_builddir] Fel 2 Makefile:66: receptet för målet ”compile” misslyckades make: *** [compile] Fel 2 Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

3 3

Re: Error building 8.1: test-pike not found
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 27 May '16

27 May '16

As a workaround, you can back your wt to 9cb2319, compile pike, and then go back to HEAD to precompile with the pike you just built.

2 1

Re: Promises in Pike vs other languages
by Chris Angelico 25 May '16

25 May '16

On Wed, May 25, 2016 at 10:30 PM, Per Hedbor () @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>I think the biggest benefit is that your async programming becomes/or >>looks more sequential/synchroneous which tend to be easier to follow, >>or in other words less spaghetti-ish. > > > And I definitely beg to differ that. > > Take this future-less code from a chat server: > > | void rpc_call_muc_join(ReturnCall x, mapping args ) > | { > | [string muc,string who] = get_args(args, > | "muc",stringp, > | "inviter",ornull(stringp)); > | > | Channel channel = get_destination( muc ); > | int when = now(); > | > | channel->when_available() > | { > | if( !channel->exists() ) > | client_error(x, "No such channel" ); > | > | channel->joined( user->id, when ) { > | me->join_channel( channel ) { > | channel->add_message( msg( "joined", > | "user_ids",({format_destination(me)}), > | "by",format_destination(me), > | "when", now)) { > | x(true); // return true. > | }; > | }; > | }; > | }; > | } > > > Todays quiz: Is it really harder to read, and how many asynchronous levels > do you think there is in it? :) If you want your asynchronous code to look truly clean, the way synchronous code does, there needs to be a way to have a function pause its execution and let something else carry on. Python can do this, either with generator functions or with the new async/await keywords. Adapting the style to Pike syntax, it'd be something like this: async string talk_to_socket(string msg) { array(string) ips = await resolv("destination.ip.address"); foreach (ips, string ip) { Stdio.File sock = Stdio.File(); sock->open_socket(); if (await sock->connect(ip, 5678)) break; } await sock->write("helo\n"); await sock->write(msg + "\n"); string data = await sock->read(1024, 1); sock->close(); return data; } Whenever you say "await", you trigger a sub-action, and the current call gets suspended. It functions pretty much like cooperative threading; effectively, any 'await' can result in a context switch. Without language support like that, everything's going to be a pile of (probably lambda) functions, one way or another. ChrisA

1 0

Re: Promises in Pike vs other languages
by Per Hedbor () ＠ Pike (-) developers forum 25 May '16

25 May '16

>Your example did not contain any definitions of functions in >functions. That's sort of debatable, since x(){} is just a shorthand syntax for x(lambda(){});, which does define a local function. :) I do see the conflict, however.

2 1

write callbacks and Stdio.File.set_buffer_mode()
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 25 May '16

25 May '16

If I set a Stdio.File object to buffer mode with both an input and an output buffer, is there a point in having a write callback registered? I can simply output data to the buffer and it will be written to the stream, right?

2 3

Re: Protocols.WebSocket client mode
by Peter Bortas 19 May '16

19 May '16

On Wed, May 18, 2016 at 6:40 PM, Marcus Agehall (nu med K-märkt fastighet och ny elcentral) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > My personal stance is that as long as you don't break existing > APIs/features, backporting new ones is not a problem. Others may > disagree with this though. That's not the whole truth. The general answer to "can I add to stable" is no. It can be added as an exception if discussed and the following is met: - The addition must be obviously safe. - It should add something that is _needed_ today. Not something that might be useful in some theoretical situation or large code cleanup. - It's checked in to the development branch before stable. Stable is a contract that should say to anyone using it that upgrades between minors are safe. Part of trying to do a release every month (in practise I predict around six successful release per year) is acctually to get stricter on this but also to make feature releases once per year. (Apparently the KOM-export script is broken again, so copy-pasting this to email. Will probably show up again whenever KOM-export gets fixed.) Regards, -- Peter Bortas

1 0

Protocols.WebSocket client mode
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 18 May '16

18 May '16

I've been spending some time in the realm of Protocols.WebSocket lately. I've been working on a client mode for it as it only contains the server side parts at the moment. I now have a working version for Pike 8.0 (which is the version that I want it for) but when I tried to port it to 8.1 I ran into a bit of a problem. It seems that the 8.1 branch has been rewritten to work with Stdio.Buffer, which is good. But from what I can tell, SSL.File does not support that API. Is there a reason for this? Also, any objections to extending the WebSocket module in 8.0 to also provide a client mode?

4 9

SSL.File()->nonblocking_mode is protected
by Chris Angelico 17 May '16

17 May '16

I'm messing around with SSL.File in a threaded server, and have run into a strange difficulty. The object defaults to nonblocking mode, which is fine; but how do I set it to blocking mode? Here's my current code: //sock is a straight Stdio.File initially string handshake = sock->read(9, 1); if (sizeof(handshake) >= 2 && handshake[0] == 0x16 && handshake[1] == 0x03) { //Probable SSL handshake Pike.SmallBackend backend = Pike.SmallBackend(); sock->set_backend(backend); sock = SSLFile(sock, SSL.Context()); write("nonblocking_mode: %O\n", sock->is_nonblocking()); sock->accept(handshake); backend->call_out(sock->set_blocking, 0); while (sock->is_nonblocking()) backend(1.0); } But this depends on being able to figure out when the socket has gone into blocking mode. To do that, I'm using my own subclass of SSL.File: class SSLFile { inherit SSL.File; int is_nonblocking() {return nonblocking_mode;} } to get around the fact that nonblocking_mode (the exact thing I'm looking for!) is flagged 'protected'. Why is this? And would an is_nonblocking method be a reasonable addition? ChrisA

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