Pike-devel October 2011

pike-devel@lists.lysator.liu.se

3 participants
12 discussions

negative indices in array ranges
by Martin Baehr 14 Aug '26

14 Aug '26

hi, instead of having to do: reverse(reverse(foo/"/")[1..]); i'd very much prefer: (foo/"/")[..-2]; are there any reasons that speak against supporting this other than me not being able to offer a patch? greetings, martin.

13 51

negative indices in array ranges
by Mirar ＠ Pike developers forum 14 Aug '26

14 Aug '26

levels might possibly be from -1 and up, -1 meaning infinite.

10 25

managing comport settings in linux
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 09 Apr '26

09 Apr '26

Not a good idea; the design philosophy of Pike is that Pike-level code should never be able to cause memory corruption at C-level. With ioctls there's no way to know what data a specific ioctl wants without reading the documentation for that specific ioctl for that specific OS. ioctls and fcntls are a way for device handlers to hook in APIs that aren't standard across all filedescriptors. / Henrik Grubbström (Lysator) Previous text: >2004-08-17 13:32: >Subject: managing comport settings in linux >-------------------------------------------------------------------- >What would be nice, is a way to define ioctl methods in >Pike. Perhaps something like > >object i = Stdio.IOCTL(4242 /* request_id */ ); >i->add_int_parameter(); >i->add_string_parameter(); >i->set_return_type(STRING); > >string ret = i(fd, 1, "somestring"); > > >That ought to be possible, or..? > > / Marcus Agehall (PacketFront) >

4 3

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 13 Mar '26

13 Mar '26

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

5 4

full MySQL 4.x support. or pike roadmap
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 01 Mar '26

01 Mar '26

HI to all! mysql 4.x support works only with a mysql CFLAGS=-DUSE_OLD_FUNCTIONS is this correct ? are there plans to make a full 4.x support ? bye, thomas

4 4

Sql.pgsql behavior in case of errors
by aldem-pikedev＠aldem.net 21 Aug '14

21 Aug '14

Hi everyone, I am preparing to use Postgres in my app, found the following strange behavior: ---snip--- Sql.Sql db = Sql.Sql("pgsql://localhost", "test", "test", "test"); db->query("BEGIN"); db->query("INSERT INTO requests (SvTrId) VALUES ('lala')"); catch(db->query("INSERT INTO requests (SvTrId) VALUES ('lala')")); db->query("INSERT INTO requests (SvTrId) VALUES ('juju')"); db->query("ROLLBACK"); ---snip--- Database is opened, row with 'lala' is inserted, second query (obviously) fails as SvTrId is the primary key, but row with 'juju' is inserted *and* appears in the database - i.e. the transaction is *committed*! Studying source code show, that once error is encounter, session is reset, i.e. running transaction is rolled back, everything is closed, temporary tables are deleted and session variables are reset as well, and after that, the next statement(s) will be committed immediately, as there is no active transaction. In my opinion, this is not exactly correct behavior when statement fails, as session still may be needed (especially temporary tables, open cursors etc). Im some cases, this is perfectly normal when SQL statement fails, especially in SERIALIZED transaction isolation level, and it would be more practical to leave the decision as of what to do to the application. Yes, this is true that it is impossible to continue executing statements in failed transaction, but temporary tables etc. may still be needed. Also, silent reconnection is not a good idea too - when there are many transactional statements are executed - it would be nice to have an option to modify this behavior. Best regards, /Alexander

5 6

pike.ida.liu.se offline?
by Ryan 18 Nov '11

18 Nov '11

I am unable to get to the pike homepage to download the latest bits and read the documents. Anyone have any information?

5 11

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

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