Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

MIME.Message problem with 7.4
by David Gourdelier 03 Feb '03

03 Feb '03

Hi list, There is a problem with Pike 7.4 and disp_params variable in MIME.Message. The following code from Caudium doesn't work with Pike 7.4. I tried to copy 7.2's MIME.pmod to Pike 7.4 MIME/module.pmod and then it was working. The difference between two MIME version is that when it works I have part->disp_params=([ /* 1 element */ "name":"1" ]), part->getdata="Upload to attachments", part->headers=([ /* 1 element */ "content-disposition":"form-data; name=\"1\"" ]) and when it doesn't work, this mapping is empty. FYI, Here is the code (from protocols/http.pike and protocols/http2.pike): case "multipart/form-data": // perror("Multipart/form-data post detected\n"); object messg = MIME.Message(data, request_headers); write("data=%O, request_headers=%O\n", data, request_headers); foreach(messg->body_parts||({}), object part) { write("part->disp_params=%O, part->getdata=%O, part->headers=%O\n", part->disp_params, part->getdata(), part->headers); if(part->disp_params->filename) { variables[part->disp_params->name]=part->getdata(); string fname=part->disp_params->filename; if( part->headers["content-disposition"] ) { array fntmp=part->headers["content-disposition"]/";"; if( sizeof(fntmp) >= 3 && search(fntmp[2],"=") != -1 ) { fname=((fntmp[2]/"=")[1]); fname=fname[1..(sizeof(fname)-2)]; } } variables[part->disp_params->name+".filename"]=fname; if(!misc->files) misc->files = ({ part->disp_params->name }); else misc->files += ({ part->disp_params->name }); } else { if(variables[part->disp_params->name]) variables[part->disp_params->name] += "\0" + part->getdata(); else variables[part->disp_params->name] = part->getdata(); } } break; Thanks for your help. -- David Gourdelier

2 4

pike startup
by Ludger Merkens 01 Feb '03

01 Feb '03

Hello, I got strange differences between the startup of pike 7.4 release 13 and pike 7.3 release 60 pike 7.3.30 doing a line like pike -I server/include/ -M server/libraries/ -P server server/server.pike will start "server.pike" pike 7.4.13 will return with: Pike: Couldn't find script to execute ("/home/balduin/cs133/pike4/steam/-M") pwd is: /home/balduin/cs133/pike4/steam doing pike --include-path=./server/include/ --module-path=./server/libraries/ --program-path=server ./server/server.pike on the other hand will work properly. yet pike --help will report the short forms as still valid --- Ludger

3 4

XPM and sort
by Mirar ＠ Pike developers forum 31 Jan '03

31 Jan '03

I finally figured out why XPM decoding is broken on my system. It uses sort() to sort the colors, but a binary comparison in a quicksearch algorithm. sort() uses strcmp. strcmp doesn't sort in binary order on my system¹. I thought it had something to do with large INT_TYPE, but now I'm convinced so isn't the case. This is the order I get: ... "*Y c #eecc22", "*Z c #ffcc22", "=` c #00dd22", "=. c #11dd22", "=+ c #22dd22", "=@ c #33dd22", "=# c #44dd22", ... Note the '`' before '.'. The bug makes the XPM module not find most of the colors, and thus rendering an almost completely black image. Could we make the Pike sort()'s strcmp compare binary? Or does anyone feel up to fixing the XPM module? (¹ appearantly, my default locale is good enough - the bug only appears if the main testsuite is run before. )

4 15

testsuite
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 31 Jan '03

31 Jan '03

The idea to rename all "module_testsuite"s to "testsuite" might not have been so bright an idea after all. The reason being, that VPATH includes "../.." in all modules (I'm not sure why though, is it really necessary?) which means the module testsuites aren't being rebuilt due to "testsuite" already being "up to date" because of ../../testsuite.

3 9

XPM and sort
by Mirar ＠ Pike developers forum 31 Jan '03

31 Jan '03

No, it isn't. The testsuite print fooled me. It's 2. Now I start to feel quite sane again :)

2 2

Re: OpenSSL wrapper vs Pike's SSL (Was: Bz2)
by Niels M�ller () ＠ Pike (-) developers forum 30 Jan '03

30 Jan '03

And I feel it's not worth the effort to try to do anything fancy with "secure deletion", mlock etc. mlock is pretty useless as it only works for root, and one don't want to encourage people to run their processes as root "for security reasons". (I'm sure not everybody agrees with that). Clearing strings and other memory when they're deallocated is reasonable, if you want to pay the extra cycles. Only question is how configurable that should be. A flag to make a particular string not appear in backtraces (or more generally, by sprintf("%O", s)) seems a little obscure, but it might be useful. Anything more complex than that? I don't think that's a good idea.

7 44

3.0 > 4.0?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 30 Jan '03

30 Jan '03

This is rather bad: Pike v7.4 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > for(int i=0; i<3.0; i++) >> if(i>4.0) error("Feh!\n"); Feh! HilfeInput:2: HilfeInput()->___HilfeWrapper() > Testsuite test committed.

3 4

zero_type() & UNDEFINED (bug?)
by Alexander Demenshin 29 Jan '03

29 Jan '03

Hi all, It is logical to expect that if zero_type(X) == zero_type(Y) then X == Y However: 0 == UNDEFINED but zero_type(0) != zero_type(UNDEFINED) this means that checks like some_value == UNDEFINED will never work correctly if some_value is an integer zero. Using zero_type() is not always convenient, at least not for readability... I suspect that this wasn't intended to operate this way, or? Regards, /Al

13 64

Bz2
by Mirar ＠ Pike developers forum 29 Jan '03

29 Jan '03

I noticed that we now have a Bz2 packer in the Pike tree. (Good job Andreas!) I did some work to get it to compile with my libbz2, and now it compiles and links fine. However, it segfaults on my machine and on some machines in xenofarm it gives funny errors in the testsuite (hence all the new yellow dots). I'm out of debugging tokens for today, so I don't mind at all if someone else makes it work... :)

18 149

CMOD and `-=
by Peta, jo det �r jag ＠ Pike developers forum 29 Jan '03

29 Jan '03

It looks like naming a function `-=() give you problems in the precompile.

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