Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Pike conference 2011 - Pike @ Roxen
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 20 Oct '11

20 Oct '11

I'll do my best to be there. Although I can't promise it matches my travel schedule. :(

1 0

[patch] better HTTP response codes
by Bill Welliver 14 Oct '11

14 Oct '11

I'm not sure if someone else has contributed something similar, but here's a patch for Protocols.HTTP.Server.Request that provides more informative response codes for almost all of the HTTP responses in widespread use (present in RFCs or not). --- lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Request.pike.orig Wed Dec 9 16:32:20 2009 +++ lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Request.pike Wed Oct 12 16:46:19 2011 @@ -31,6 +31,79 @@ // finalize +constant errors= +([ + // Informational + 100:"100 Continue", + 101:"101 Switching Protocols", + 102:"102 Processing", // WebDAV + 103:"103 Checkpoint", + 122:"122 Request-URI too long", // a non standard IE7 error + + // Successful + 200:"200 OK", + 201:"201 Created, URI follows", + 202:"202 Accepted", + 203:"203 Non-Authoritative Information", + 204:"204 No Content", + 205:"205 Reset Content", + 206:"206 Partial Content", // Byte ranges + 207:"207 Multi-Status", // WebDAV + 226:"226 IM Used", // RFC 3229 + + // Redirection + 300:"300 Moved", + 301:"301 Permanent Relocation", + 302:"302 Found", // a potential alligator swamp. for HTTP/1.1, use 303/307. + 303:"303 See Other", // temporary redirect, any POST data is received, use GET. + 304:"304 Not Modified", + 305:"305 Use Proxy", + 306:"306 Switch Proxy", // Deprecated + 307:"307 Temporary Redirect", // retry request elsewhere, don't change method. + 308:"308 Resume Incomplete", + + // Client Error + 400:"400 Bad Request", + 401:"401 Access denied", + 402:"402 Payment Required", + 403:"403 Forbidden", + 404:"404 No such file or directory.", + 405:"405 Method not allowed", + 406:"406 Not Acceptable", + 407:"407 Proxy authorization needed", + 408:"408 Request timeout", + 409:"409 Conflict", + 410:"410 Gone", + 411:"411 Length Required", + 412:"412 Precondition Failed", + 413:"413 Request Entity Too Large", + 414:"414 Request-URI Too Large", + 415:"415 Unsupported Media Type", + 416:"416 Requested range not statisfiable", + 417:"417 Expectation Failed", + 418:"418 I'm a teapot", // Ha ha + 422:"422 Unprocessable Entity", // WebDAV + 423:"423 Locked", // WebDAV + 424:"424 Failed Dependency", // WebDAV + 425:"425 Unordered Collection", // RFC3648 + 426:"426 Upgrade Required", // RFC2817 + + // Internal Server Errors + 500:"500 Internal Server Error.", + 501:"501 Not Implemented", + 502:"502 Bad Gateway", + 503:"503 Service unavailable", + 504:"504 Gateway Timeout", + 505:"505 HTTP Version Not Supported", + 506:"506 Variant Also Negotiates", // RFC2295 + 507:"507 Insufficient Storage", // WebDAV / RFC4918 + 509:"509 Bandwidth Limit Exceeded", // An Apache defined extension in popular use + 510:"510 Not Extended", // RFC2774 + 598:"598 Network read timeout error", // Informal extension used by some HTTP proxies + 599:"599 Network connect timeout error", // Informal extension used by some HTTP proxies +]); + + int max_request_size = 0; void set_max_request_size(int size) @@ -475,15 +548,12 @@ m->error=206; } break; - case 302: - res+=({protocol+" 302 TEMPORARY REDIRECT"}); - break; - case 304: - res+=({protocol+" 304 Not Modified"}); - break; default: // better error names? - res+=({protocol+" "+m->error+" ERROR"}); + if(errors[(int)m->error]) + res+=({protocol+" " + errors[(int)m->error]}); + else + res+=({protocol+" "+m->error+" ERROR"}); break; }

4 5

[patch] allow multiple parts of a multipart form with the same name
by H. William Welliver III 13 Oct '11

13 Oct '11

Here's another patch that I'm a little less sure about. Currently, if you submit a multipart form that has more than 1 part with a given name, only the last part is included in the request object (the others are overwritten). I've run into a few applications that expect such a submission to be treated as an array (for example, multiple files uploaded this way is part of the HTML5 'spec'). The following patch enables that behavior. --- lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Request.pike.orig 2011-10-07 01:32:42.000000000 -0400 +++ lib/modules/Protocols.pmod/HTTP.pmod/Server.pmod/Request.pike 2011-10-12 21:38:23.000000000 -0400 @@ -388,18 +387,9 @@ foreach(messg->body_parts, object part) { if(part->disp_params->filename) { + if(variables[part->disp_params->name] && !arrayp(variables[part->disp_params->name])) + variables[part->disp_params->name] = ({ variables[part->disp_params->name] }); + if(variables[part->disp_params->name] && arrayp(variables[part->disp_params->name])) + variables[part->disp_params->name] += ({part->getdata()}); + else variables[part->disp_params->name]=part->getdata(); + + if(variables[part->disp_params->name+".filename"] && !arrayp(variables[part->disp_params->name+".filename"])) + variables[part->disp_params->name+".filename"] = ({ variables[part->disp_params->name+".filename"] }); + if(variables[part->disp_params->name+".filename"] && arrayp(variables[part->disp_params->name+".filename"])) + variables[part->disp_params->name+".filename"] += ({part->disp_params->filename}); + else + variables[part->disp_params->name+".filename"]= part->disp_params->filename; - variables[part->disp_params->name]=part->getdata(); - variables[part->disp_params->name+".filename"]= - part->disp_params->filename; } else variables[part->disp_params->name] = part->getdata(); }

1 0

multiset difference incorrect?
by Martin Bähr 12 Oct '11

12 Oct '11

hi, according to http://topdefinitions.com/multisets-and-their-operations/ the difference between multisets is defined as: The difference of two multisets A and B, is a multiset such that the multiplicity of an element is equal to the multiplicity of an element in A minus multiplicity of an element in B, if the difference is +ve, and it is equal to 0 if the difference is 0 and –ve. It is denoted by A-B. e.g. A={l,l,m,m,m,n,n} B={l,m,m,n,n,n} A-B={l,m} however in pike: > multiset A =(< "l","l","m","m","m","n","n">); > multiset B =(< "l","m","m","n","n","n">); > A-B; Result: (< >) greetings, martin.

2 1

ADT.Set does not support ^; & operator fails in hilfe
by Martin Bähr 10 Oct '11

10 Oct '11

> ADT.Set AAS = ADT.Set(({ "John", "Serena", "Bob", "Mary", "Serena", "Bob" })); > ADT.Set BAS = ADT.Set(({ "Jim", "Mary", "John", "Jim", "Bob", "Mary" })); > AAS^BAS; Operator not in object. Unknown program: `^(ADT.Set({ /* 4 elements */ "Bob", "Serena", "John", "Mary" }),ADT.Set({ /* 4 elements */ "Bob", "John", "Mary", "Jim" })) HilfeInput:1: HilfeInput()->___HilfeWrapper() the error below only appears in hilfe: > AAS&BAS; Compiler Error: 1: Undefined identifier AAS. Compiler Error: 1: Undefined identifier BAS. Compiler Error: 1: Too few arguments to `& (got 0). Compiler Error: 1: Expected: array | mapping | multiset | object | program | string | type(mixed) | int | mixed. Compiler Error: 1: Function type: Compiler Error: 1: Got : scope(0,function((0=mixed) : 0) | function((0=program | type(mixed)) : 0) | function((0=string) : 0) | function((0=multiset) : 0) | function((0=mapping) : 0) | function((0=array) : 0) | function((0=int) : 0) | function(mixed, object, mixed ... : mixed) | function(object, mixed, mixed ... : mixed) | !function(!mapping ... : mixed) & function(array | multiset | (4=mapping) ... : 4) | !function(!(program | type(mixed)) ... : mixed) & function((1=program | type(mixed)), (2=program | type(mixed)) ... : 1 | 2) | !function(!string ... : mixed) & function((1=string), (2=string) ... : 1 | 2) | !function(!multiset ... : mixed) & function((1=multiset), (2=multiset) ... : 1 | 2) | !function(!mapping ... : mixed) & function((1=mapping), (2=mapping) ... : 1 | 2) | !function(!array ... : mixed) & function((1=array), (2=array) ... : 1 | 2) | !function(!int ... : mixed) & function((1=int), (2=int) ... : 1 | 2)). greetings, martin.

1 0

Re: Possible bug walking a GTK2.TreeModel in 7.9
by Lance Dillon 22 Sep '11

22 Sep '11

----- Original Message ---- > From: larcky <pclar7(a)yahoo.co.uk> > To: pike(a)roxen.com > Sent: Thu, September 22, 2011 3:17:33 AM > Subject: Possible bug walking a GTK2.TreeModel in 7.9 > > Hi > This works fine in Pike 7.8 but 7.9 crashes with a Segmentation Fault. I > think the problem's with GTK2.TreeModel->iter_next(). I can get the first > row OK but then the iterator becomes invalid. > Thanks, larcky > I believe I see the problem. In 7.9, in gtktreemodel.pre, function iter_next, it was changed to push the iter onto the stack, to return it. This way you can possibly do things like iter2=tm->iter_next(iter). The problem is that iter gets modified in place by gtk_tree_model_iter_next(), so it is there, then it gets pushed onto the stack also. So the same GtkTreeIter is present twice, once in the original object, and another on the stack. When the one on the stack doesn't get assigned to anything, it gets free'd by gtk, so the original iter gets free'd also. Then when you try to use it again, possibly the memory is fine and hasn't been overwritten yet, but when it tries to free it again, it gets the double free. 7.9 needs to be changed to either copy the iter, or to not return it. Does anybody have a preference? I don't think the copy would be the right thing to do, because it would usually consist of a copy and a free anyway, because you won't probably won't use the old one once you have the next one. I don't think there is any way to do it otherwise because gtk_tree_model_iter_next() replaces the iter, it doesn't return the next one as a new iter, leaving the old one alone.

1 1

Re: Val.true and Val.false [Was: XMLRPC] (from pike@roxen.com)
by Lance Dillon 11 Sep '11

11 Sep '11

Patch for boolean support for Protocols.XMLRPC --- module.pmod.orig 2011-08-31 16:02:19.838058384 -0400 +++ module.pmod 2011-09-07 10:17:21.848427570 -0400 @@ -15,12 +15,15 @@ //! Pike @expr{mapping@} is translated to XML-RPC @tt{<struct>@}. //! Pike @expr{array@} is translated to XML-RPC @tt{<array>@}. //! Pike @[Calendar] object is translated to XML-RPC @tt{<dateTime.iso8601@}. +//! Pike @expr{Val.false@} and @expr{Val.true@} is translated to +//! XML-RPC @tt{<boolean>@}. //! //! Translation rules for conversions from XML-RPC datatypes to Pike //! datatypes: //! -//! XML-RPC @tt{<i4>@}, @tt{<int>@} and @tt{<boolean>@} are -//! translated to Pike @expr{int@}. +//! XML-RPC @tt{<i4>@} and @tt{<int>@} are translated to Pike @expr{int@}. +//! XML-RPC @tt{<boolean>} is translated to Pike @expr{Val.true@} and +//! @expr{Val.false@}. //! XML-RPC @tt{<string>@} and @tt{<base64>@} are translated to //! Pike @expr{string@}. //! XML_RPC @tt{<double>@} is translated to Pike @expr{float@}. @@ -225,8 +228,9 @@ return sizeof(data)?data[0]:""; case "i4": case "int": - case "boolean": return (int)(data*"") || magic_zero; + case "boolean": + return ((int)(data*""))?Val.true:Val.false; case "double": return (float)(data*""); case "string": @@ -274,7 +278,7 @@ ({ "&", "<", ">", """, "'", "" })); } -protected string encode(int|float|string|mapping|array value) +protected string encode(int|float|string|mapping|array|object value) { string r = "<value>"; if(intp(value)) @@ -303,6 +307,8 @@ else if (objectp (value) && value->format_iso_short) r += "<dateTime.iso8601>" + value->format_iso_short() + "</dateTime.iso8601>"; + else if (objectp(value) && (value->is_val_true || value->is_val_false)) + r += sprintf("<boolean>%d</boolean>",(int)value); else error("Cannot encode %O.\n", value); return r+"</value>\n";

3 16

Re: Val.true and Val.false [Was: XMLRPC] (from pike@roxen.com)
by Lance Dillon 10 Sep '11

10 Sep '11

Okay I'll take care of that this afternoon. Sent from Yahoo! Mail on Android

1 0

pikefarm
by Lance Dillon 09 Sep '11

09 Sep '11

It looks like pikefarm isn't valid anymore. I went to this page: http://pike.ida.liu.se/development/pikefarm/7.8.xml, and it looks like the latest build was on 2010-10-01 16:15:54 (1197). Is it still being used, or is there a different url to go to?

1 0

Re: Val.true and Val.false [Was: XMLRPC]
by Lance Dillon 07 Sep '11

07 Sep '11

> > > Looks ok, but could you please update the docs accordingly as well? > > > > Getting (optional) boolean support when decoding would be nice from a > > feature and symmetry perspective, but that's not a requirement imo. > > > > > In order to backport Val.pmod to 7.8.526, I had to remove Null, because >it > > > references Builtin.Null, which doesn't exist. > > > > Right. That shouldn't be a problem in this case. > > > That last patch was for 7.8.526 with Val.pmod backported (meaning, minus Val.Null) to add boolean support to Protocols.XMLRPC using Val.

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