Pike-devel September 2016

pike-devel@lists.lysator.liu.se

7 participants
16 discussions

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

07 Oct '16

Something I would recommend, from having written heaps of asynchronous object based systems, with or without remote computers involved, is to treat all references to the promise object going away as an error, and avoid un-needed circular references. This makes it easy to detect when you accidentally forget the object. Also, having the object be callable is rather convenient, it can then be put as a normal callback in all the various function based API:s we already have. >From the MiniRPC module, used extensively in the mini codebase: // This is an object representing a function to be called when // whatever task is being requested has been completed. // // In the RPC case the 'call_id' and 'par' are used to send the return // value, and function_name is for debug purposes. // class ReturnFromCall(protected int call_id, protected object par, protected string function_name) { protected void destroy() { // this should check the done function callback instead.. if( call_id ) { werror("Return was never called for "+function_name+"\n"); if( par ) this.error("Return was never called\n"); } } protected string _sprintf( int flag, mapping opts ) { // It's rather nice to have a _sprintf for backtraces. But // without a function_name it's harder :) return sprintf("ReturnCall(from %O)", function_name ); } protected void error(string err) { // .. this is sort of special in the RPC code .. call_id = 0; destruct(this); } void `()(mixed ... x ) { // Wanted addition #2: Callable promises? call_id = 0; destruct(this); } mixed try( function x ) //! Call @[x], if the call fails report an error message to //! the remote side. // // syntax of the day: // foo( foo->try() { code to run..; return res;}); // // It might be useful to have a functon that also returns the // value calculated { if( mixed err = catch{return x();}) { // code goes here to log etc.. this.error(err); } } } Also, I personally belong to the "future/promises don't really add much" camp, but feel free to add the API. :) (In my opinion it's just another way to complicate asynchronous programming)

4 7

Clean-room Socket.IO implementation committed to git 8.0/8.1
by Stephen R. van den Berg 28 Sep '16

28 Sep '16

Please review, any comments are welcome. The docs still need improvement, working on that. Trying to do this one from the specs results in the same sorry mess as Engine.IO. So this again is the result of "specs" combined with a lot of protocol reverse engineering. -- Stephen.

1 4

Multiple function prototype declarations
by Stephen R. van den Berg 23 Sep '16

23 Sep '16

I seem to recall that in C, one can define multiple function declarations for the same function. Is it possible to do the same at Pike level? Example, I have a function declared as void foo(mixed ... bar); Now I want to check, and enforce two different declarations: void foo(string s, mixed ... bar); void foo(function f, string s, mixed ... bar); Can I, at Pike level, declare somehow that the above two prototypes are the only two valid prototypes for this function? So that Pike will give me a syntax error if I try to do foo(23); ? -- Stephen.

2 2

Re: Setting socket options: so many, uhh, options!
by Chris Angelico 15 Sep '16

15 Sep '16

On Tue, Mar 10, 2015 at 10:05 PM, Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Wait, I said REUSEPORT? What's the difference to REUSEADDR? Mysteries > of TCP sockets... Here's a decent explanation, I think: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and… ChrisA

3 6

Compile error in 8.1
by Pontus Östlund 14 Sep '16

14 Sep '16

Hi guys! Does anyone know how to solve this? make[2]: *** No rule to make target '/home/poppa/src/pike-git/devel/src/hashtable.h', needed by 'cpp.o'. Stop. Makefile:149: recipe for target '_make_in_builddir' failed make[1]: *** [_make_in_builddir] Error 2 Makefile:66: recipe for target 'compile' failed make: *** [compile] Error 2 It seems to have happend after commit dcf57dec52f15cda0dc07bbaf2198a250b37030c 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>

2 3

Winsock error 10038 when backending sockets and stdin
by Chris Angelico 12 Sep '16

12 Sep '16

On Unix, you can happily select() on any file descriptors, including stdin and sockets. On Windows, that doesn't appear to be the case. Here's a simple form of netcat: object sock; void sockread(mixed id, string data) { //Restrict to ASCII printables for simplicity write(filter(data, lambda(int c) {return has_value("\t\r\n", c) || (c >= 32 && c < 128);})); } void console(mixed id, string data) {sock->write(data);} int main() { sock = Stdio.File(); sock->connect("minstrelhall.com", 221); sock->set_read_callback(sockread); Stdio.stdin->set_read_callback(console); return -1; } The important aspects of this are read callbacks on both a socket and Stdio.stdin, and returning -1 from main. Comment out the stdin callback and all is well. Keep it in, and the program runs fine on Unix, but on Windows, bombs out: /home/zino/hack/pike8-rel/pike/src/backend.cmod:5496: Fatal error: Filedescriptor 0 (IS CONSOLE) caused fatal error 10038 in backend. Backtrace at time of fatal: -:1: Pike.Backend(0)->`()(3600.0) This happens with both 7.8 and 8.0 stables on Windows 7, though I doubt it'll be any different on other Pikes or Windowses. Is there any good way to respond to console and sockets? For now, I think I'll just write this off as "Windows sucks" and disable the console (it's only a debug/emergency feature anyway). ChrisA

1 0

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