Pike-devel July 2005

pike-devel@lists.lysator.liu.se

8 participants
24 discussions

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

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

13 Jul '05

I thought that this was fixed a while back, but the latest 7.7 precompile.pike gives me errors: precompile: /usr/local/pike/7.7.19/bin/pike /usr/local/pike/7.7.19/include/pike/precompile.pike Node.cmod Cannot index the NULL value with 0. /usr/local/pike/7.7.19/include/pike/precompile.pike:1398: /main()->generate_overload_func_for(({FuncData(f_Node_copy_1_defined),Func Data(f_Node_copy_2_defined)}),2,0,2147483647,"copy",mapping[1]) /usr/local/pike/7.7.19/include/pike/precompile.pike:2164: /main()->ParseBlock()->create(({({,,,18}),({,,,3}),({,,,4}),({,,,4}),({,,, 4}),({,,,4}),({,,,4}),({,,,4}),({,,,4}),({,,,4}),({,,,4}),({,,,4}),({,,,4} ),,,38}),"Node") /usr/local/pike/7.7.19/include/pike/precompile.pike:177: /main()->ParseBlock() /usr/local/pike/7.7.19/include/pike/precompile.pike:1509: /main()->ParseBlock()->create(({"/* Generated from \"Node.cmod\" by precom pile.pike\n *\n * Do NOT edit this file.\n */\n","\n#undef PRECOMPILE_API_ VERSION\n","#define PRECOMPILE_API_VERSION 2\n","\n\n",,,25}),"") /usr/local/pike/7.7.19/include/pike/precompile.pike:177: /main()->ParseBlock() /usr/local/pike/7.7.19/include/pike/precompile.pike:2305: /main()->main(2,({"/usr/local/pike/7.7.19/include/pike/precompile.pike","Node.cmod"})) Failed to run /usr/local/pike/7.7.19/include/pike/precompile.pike. When presented with the following code: PIKEFUN object copy() { struct object * o; xmlNodePtr node; check_node_created(); node = xmlCopyNode(THIS->object_data->node, 0); o=NEW_NODE(); OBJ2_NODE(o)->object_data->node = node; OBJ2_NODE(o)->object_data->unlinked = 1; NEW_NODE_REFS(o); push_object(o); } PIKEFUN object copy(int extended) { xmlNodePtr node; check_node_created(); node = xmlCopyNode(THIS->object_data->node, extended); o=NEW_NODE(); OBJ2_NODE(o)->object_data->node = node; OBJ2_NODE(o)->object_data->unlinked = 1; NEW_NODE_REFS(o); push_object(o); } Any suggestions? Bill

1 0

dirnodes
by Martin Nilsson (DivX Inc.) ＠ Pike (-) developers forum 13 Jul '05

13 Jul '05

I've just checked in a fix that makes the resolver code in the master even uglier as well as making it possible to do both -> and [] on dirnodes and joinnodes. Feedback is good.

5 25

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

12 Jul '05

By normal operator I mean that it could work on non-constant objects too. And to change the resolver to return objects flagged as constant-index-optimize as long as only modules or submodules are indexed. Then you could do things like | #ifdef DYNAMIC_LOAD | class dynload( string module ) | { | object real; | mixed `->(string x) { | if( !real ) real = master()->resolv( module ); | return predef::`->(real,x); | } | } | object Protocols = dynload("Protocols"); // Dynamically loads Protocol | // module on demand. | #endif | | void get_url( ) | { | Protocols.HTTP.get_url_nice( ... ); // <-- equivalent to HTTP->get_url_nice | } | and have minimal codechanges to implement dynamic loading (nothing has to change in the code using the Protocol.whatever modules, only change needed is the existance of the class-global Protocols object).

2 2

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

12 Jul '05

Or, for that matter, `.()

1 0

Re: make_shared_string()
by H. William Welliver 11 Jul '05

11 Jul '05

I think push_text() is just a macro for the code you listed there. I'd say about half of the commonly used helper functions are really convenience macros. Unfortunately, most aren't documented :/ It would be interesting to know what the various make_*_string() are used for... Bill On Jul 11, 2005, at 3:54 PM, Lance Dillon wrote: > I've been using push_text(s), but I saw in another file the person > used: > > struct pike_string *str; > str=make_shared_string(s); > push_string(str); > > What would the benefit, if any, of the above code be over using > push_text()? > > thanks.. >

1 0

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 July 2005