Pike-devel May 2004

pike-devel@lists.lysator.liu.se

11 participants
65 discussions

Quoting in Standards.URI
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 26 May '04

26 May '04

Seems like Standards.URI do neither encoding nor decoding according to rfc 2396: Pike v7.7 release 3 running Hilfe v3.5 (Incremental Pike Frontend) > object uri = Standards.URI("http://foo/a%3Fb?c"); > uri->path; (1) Result: "/a%3Fb" > _Roxen.http_decode_string (uri->path); (2) Result: "/a?b" > uri->path = _; (3) Result: "/a?b" > (string) uri; (4) Result: "http://foo/a?b?c" Is it per design? I think it's pretty clear that it should handle this detail too. Unfortunately it's quite a problem to change that now since this class already is used extensively, and changes in quoting behavior is one of the most notorious compatibility problem generators. Someone got any idea about how common it is that calling code "works around" this by doing its own encoding and decoding?

4 8

Quoting in Standards.URI
by Johan Sch�n (Firefruit) ＠ Pike (-) developers forum 26 May '04

26 May '04

Python's urlparse module also doesn't unescape: http://docs.python.org/lib/module-urlparse.html

1 0

Quoting in Standards.URI
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 May '04

26 May '04

Another one might be Subverson URL:s, if support for filenames containing "/" is ever added (could be used on old MacOS). There didn't seem to be much incentive for doing this last time I checked though. :-)

1 0

Process.create_process in 7.6
by Bill Welliver 25 May '04

25 May '04

It appears that one can no longer pass a Stdio.Port() object as stdin to Process.create_process. We had been using this method to process FastCGI, but now with 7.6, it seems that passing a Stdio.Port in options->stdin throws an error. Does anyone know if this was an intentional change or whether there's a workaround? Bill

2 1

Bittorrent bugs
by Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum 25 May '04

25 May '04

How serious are these kind of errors? Got POLLERR on non-socket fd 173 (getsockopt errno=9) Got POLLERR on non-socket fd 197 (getsockopt errno=9) Got POLLERR on non-socket fd 99 (getsockopt errno=9) Got POLLERR on non-socket fd 92 (getsockopt errno=9) Got POLLERR on non-socket fd 174 (getsockopt errno=9) Got POLLERR on non-socket fd 70 (getsockopt errno=9) Got POLLERR on non-socket fd 58 (getsockopt errno=9) Got POLLERR on non-socket fd 159 (getsockopt errno=9)

2 3

Pike 7.2 not exported
by David Gourdelier 24 May '04

24 May '04

Hi, While trying the Pike 7.2 official releases at ftp://pike.ida.liu.se/pub/pike/all/7.2.239/ and ftp://pike.ida.liu.se/pub/pike/all/7.2.197/, I saw these versions are not exported: Compiling /home/david/archives/Pike-v7.2.197/src/queue.c ./precompile.sh precompile.pike >"/home/david/archives/Pike-v7.2.197/src/builtin.c" "/home/david/archives/Pike-v7.2.197/src/builtin.cmod" || { rm "/home/david/archives/Pike-v7.2.197/src/builtin.c"; exit 1; } precompile: /home/david/archives/Pike-v7.2.197/src/pike -DNOT_INSTALLED -m/home/david/archives/Pike-v7.2.197/src/master.pike ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=Q) ./precompile.sh: /home/david/archives/Pike-v7.2.197/src/pike: not found precompile: /home/david/archives/Pike-v7.2.197/src/tpike -DNOT_INSTALLED -m/home/david/archives/Pike-v7.2.197/src/master.pike ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=QQ) ./precompile.sh: /home/david/archives/Pike-v7.2.197/src/tpike: not found precompile: /home/david/archives/Pike-v7.2.197/src/test-pike ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=QQQ) ./precompile.sh: /home/david/archives/Pike-v7.2.197/src/test-pike: not found precompile: pike -DOLD ./precompile.pike /home/david/archives/Pike-v7.2.197/src/builtin.cmod (method=QQQQQQ) pike: not found blabla.... / David

1 0

Re: Suggestions to manual
by Martin Bähr 19 May '04

19 May '04

i am changing the list, as this is not relevant for pike users. On Tue, May 18, 2004 at 03:46:44PM +0200, Martin Stjernholm wrote: > > mixed m; > > typeof(m); > (1) Result: mixed > > typeof([int] m); > (2) Result: int > > Only the type is changed, hence a type cast. A normal cast like > (int) "1" changes the value, hence a value cast. the difference is than that [type] only changes the variable but not its value, whereas (type) changes both. in other languages (see the c and java examples), the term "type cast" is used to describe the first case where where both variable and value are changed. hence i think it is a bad idea to use a different definition in pike. coining new terms is fine, but chaning existing ones will lead to confusion. "variable cast" might work. greetings, martin.

5 5

Syslog fix
by David Gourdelier 19 May '04

19 May '04

Hi, I think there is a bug in system/syslog.c: if(i & (1<<0)) pri |= LOG_EMERG; if(i & (1<<1)) pri |= LOG_ALERT; if(i & (1<<2)) pri |= LOG_CRIT; if(i & (1<<3)) pri |= LOG_ERR; if(i & (1<<4)) pri |= LOG_WARNING; if(i & (1<<5)) pri |= LOG_NOTICE; if(i & (1<<6)) pri |= LOG_INFO; if(i & (1<<6)) pri |= LOG_DEBUG; Shouldn't it be 1<<7 instead of 1<<6 for the last line ? -- David Gourdelier

2 1

some observations on the build process
by Martin Bähr 19 May '04

19 May '04

hi, when building pike 7.6 from cvs i noticed a few things that could be improved: after configure a summary of what was detected is shown. but when you just run make as suggested then you never see that summary because it gets buried in the compile outbut following it. hence it would be nice to show that summary after a complete make run as well. after finding that a lot of libs were missing to build GL and all that i found that after installing them neither make force_autoconfig nor make force_configure not even make clean would do anything to update the findings. i had to remove the whole build tree to get the new libs detected. greetings, martin.

9 12

Pike @ win32
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 19 May '04

19 May '04

I've just committed an initial patch that allows Pike to be compiled using mingw32. To compile pike using mingw32, you will have to do the following: 1) Install the latest mingw32-dist 2) Install Msys 3) Install the mingw Win32 API update 4) Install GMP (either from source or bin package) 5) Install Nettle (untested! I've been using --without-nettle for the time beeing...) 6) Get a Pike 7.7 source snapshot (or build one yourself). Building from CVS under mingw32 seems to break due to some cr/lf problem, so build the source-dist on a unix box. 7) Set the PIKE_PATH_TRANSLATE to some sed-command which translates the master-paths from you MSYS installation to the regular NT-CMD filesystem(*). 8) Do "make configure" to configure your buildtree. 9) Do "make" do build pike. 10) (optional) Do "make verify". This will fail, the hard way.. ;( 11) You should now have a pike which is usable to some extent. I havn't tested it much, but I've done some simple tests and it seems to hold up fairly well. (*) I build from my home-dir, /home/SSS668. To create a working master, I need to translate that path to c:/msys/1.0/home/SSS668. You need to do the same using some creative sed-command or accept that your build will fail when it attepmts to build post_modules. You can modify the master manually if you like. Look for the ¤-sign to find what places to modify. So, there it is. Now you should know what you need to build. I believe that Mingw32 is the easiest way to get Pike to compile on Win32. However, I'm not so certain it is the best choice since there seems to be quite a few compatibility issues between mingw32 and the win32 api (as MS provides it). I have access to both at work and they do not match in several places. I believe that we should try to get Pike to work with mingw first, and then start working towards MSVC native compilation. However, there will still be the problem of configuring the build. It may be that we always will need a msys-layer to run configure.

5 9

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 May 2004