Pike-devel

pike-devel@lists.lysator.liu.se

3044 discussions

automap: [*] not supported here. bug?
by Martin Bähr 23 Jul '05

23 Jul '05

hi, can you explain why: random(allocate(3,9)[*]); or random(({9,9,9})[*]); don't work, while array foo = allocate(3,9); random(foo[*]); does? greetings, martin.

6 13

Re: Pike 7.6
by Peter Bortas ＠ Pike developers forum 23 Jul '05

23 Jul '05

>so while it would be nice to have in 7.6, It would, and I want it there, but it needs to sit in 7.7 for a while so people get a sproting chance at checking out the interface before it's cast in stone.

1 0

Binary size
by Martin Nilsson (DivX Inc.) ＠ Pike (-) developers forum 23 Jul '05

23 Jul '05

Something strange has happened with the pike 7.7 binary during the last month or so. It used to be 4.6 MB, but is now 15.4 MB when looking with ls. Using size however tells that the text segment is down 34k and the rest remains unchanged since May. What's the padding?

3 2

file->write
by Credence Shanden 22 Jul '05

22 Jul '05

I upgraded from pike v7.4.44 to 7.6.24 and now I can no longer write to files using the same code I used from before. Instead I get an error stating: Bad argument 1 to file->write(). Type is int. Expected string or array(string) _static_modules.files()->Fd: Fd(1)->write(0) Below is the code I am using to do so: void CompileError ( string file, int line, string err ) { string sFile; object ferr = Stdio.File("C:/EMAGE/sys/data/log/comp.c", "wca+"); sscanf(file, "C:/EMAGE%s", sFile); string sOut = sFile + ": " + (string)line + "-" + err + "\t" + ctime(time()); ferr->write("%s:%s:%s\t%s\n", sFile, line?(string)line:"-",err, ctime(time())); ferr->close(); } I have tried several variations of this to no avail. Including: if(stringp(sOut)) { object o = Stdio.File(); if(o) { if(o->open("C:/EMAGE/sys/data/log/comp.c", "wca", 0777)) { if(o->write(sOut)) { return; } } } } __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

postgresql fix
by Marc Dirix 16 Jul '05

16 Jul '05

This is a fix for the postgresql module, which didn't correctly parse its arguments. Argument 5 was not parsed correctly. === postgres.c ================================================================== --- postgres.c (revision 34286) +++ postgres.c (local) @@ -255,12 +255,12 @@ switch(args) { default: case 5: - if (Pike_sp[2-args].type==PIKE_T_INT && /*this check is maybe redundant*/ - Pike_sp[2-args].u.integer <=65535 && - Pike_sp[2-args].u.integer >= 0) { - if (Pike_sp[2-args].u.integer>0) { + if (Pike_sp[4-args].type==PIKE_T_INT && /*this check is maybe redundant*/ + Pike_sp[4-args].u.integer <=65535 && + Pike_sp[4-args].u.integer >= 0) { + if (Pike_sp[4-args].u.integer>0) { port=xalloc(10*sizeof(char)); /*we only need 6, we just checked.*/ - sprintf(port,"%"PRINTPIKEINT"d",Pike_sp[2-args].u.integer); + sprintf(port,"%"PRINTPIKEINT"d",Pike_sp[4-args].u.integer); } } case 4:

2 1

dirnodes
by Per Hedbor () ＠ Pike (-) developers forum 15 Jul '05

15 Jul '05

Having . as a normal operator equivalent to `-> instead of `[] would make more sense than the current situation. I doubt that there is a lot of code depending on . beeing `[] and not `->.

4 9

Calendar woes
by Jonas Walld�n ＠ Pike developers forum 15 Jul '05

15 Jul '05

I'm trying to use the Calendar module in 7.4 for some basic stuff: > Calendar.ISO.Day(2005, 03, 30); (36) Result: Day(Wed 30 Mar 2005) > Calendar.ISO.Day(2005, 03, 30) - Calendar.ISO.Month(); (37) Result: Day(Wed 2 Mar 2005) Is that the expected output? I'd love to hear the rationale for that. :-) (BTW, 7.7 returns the same so it's not a 7.4 issue.) More importantly, how can I accomplish month-by-month stepping that pins the day number within the prev/next month? Of course one method would be to create Month objects manually and compare days etc but I figure it's probably already solved.

5 8

broken threading
by Marc Dirix 14 Jul '05

14 Jul '05

I'm currently working on a bug in Chilimoon. The problem is we're getting the following error messages: Backend already in use by another thread. _static_modules.Builtin()->Backend: Pike.Backend(0)->`()("Backend already in use by another thread.\n") This error comes from backend.cmod. After doing some research I've discovered the bug occurs after an cvs checkin of backend.cmod in pike on 2005-01-20. r1.161 is working, r1.163 isn't. It might be possible this checkin breaks the shuffler which is used by Chilimoon, and not by Roxen Webserver. Roxen Webserver does not have the same problem.

2 3

dirnodes
by Per Hedbor () ＠ Pike (-) developers forum 14 Jul '05

14 Jul '05

As an example, Image.load could not load from URL:s since pike 7.4 or so. The reason being that Nilsson wanted to load the HTTP module dynamically, but did not know about the difference between -> and [], with regard to dirnode modules. Personally I thought that the support for loading from URL:s was simply removed for some other reason, and never investigated more closely.

3 2

Re: CMOD polymorphic overloading (again)
by Bill Welliver 13 Jul '05

13 Jul '05

It looks like the problem is found around line 1292: when one of the possible methods has zero arguments, this check will fail, and the information for the zero arguments case will not be collected: if(min_args) ... I changed it to if(min_args>=0) and the code is generated properly. I'm not sure that it's the proper fix to the problem, you'd probably have to change the initial value for min_args to be -1 or something when the zero args case as not an option. Bill

1 0

Jump to page:

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