Pike-devel December 2004

pike-devel@lists.lysator.liu.se

7 participants
27 discussions

hilfe bug?
by Martin Bähr 20 Apr '05

20 Apr '05

Pike v7.6 release 7 running Hilfe v3.5 (Incremental Pike Frontend) > int year=2004; > int month=12; > int day=2; > object oday = Calendar.Year(year)->month(month)->day(day); Compiler Error: 1:syntax error, unexpected '(' Compiler Error: 1:syntax error, unexpected '(' > ??? can anyone explain this? greetings, martin.

6 8

Pike string hashing
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 20 Apr '05

20 Apr '05

I'm a bit curious about the string hashing algorithm used in Pike. What algorithm is it based on and what complexities does it exhibit? Was it selected at random or is there some rationale behind it..?

3 5

MySQL big_query in 7.7
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 10 Apr '05

10 Apr '05

I think the new streaming behavior in Sql.mysql.big_query is nice and as it should be, but it's causing too much headaches in existing applications - the old de-facto behavior is too ingrained. So a proposal is to instead do like this: query: Like today - slow and memory consuming. big_query: A variant of query() that still is nonstreaming. I.e. it only avoids the very bulky response format of query(). streaming_query: Like big_query but guaranteed to stream if it exists. It's database dependent whether other queries can be issued while a streaming_query response object exists. It's of course also database dependent if there are locks on the tables in the server while the response object exists. While at it, we could also consider generalizing the big_typed_query interface that the oracle module provides: big_typed_query: Like big_query but doesn't convert everything to strings. Integers and floats are kept that way, Date/timestamps are Calendar objects, there are objects for representing the NULL value for each type. streaming_typed_query: Streaming variant of big_typed_query.

9 20

pmod compilation & inherits
by Kaos 27 Jan '05

27 Jan '05

Hi, Does anyone have any clue what I'm doing wrong here ? The directly involved files are: RemoteObjectModel.pmod/ module.pmod Proxy.pike Service.pike ServerObject.pike ClientObject.pike In proxy, I have a class that inherits ServerObject, which it fails for here. But if I change it from inherit .ServerObject; to inherit "ServerObject.pike"; // works nice but then there's the next problem: if I add another file in this directory and tries to access it from module.pmod with .Foo (i.e. for Foo.pike) it fails with the same error as below (but with different names, naturally) I've tried to build up a similar situation with simple files, and there it works just fine. Any clues? Pike version: 7.6.25 <side-issue> If I would like to use the `-> and `[] lfun's in module.pmod, how do I resolve the modules/programs further down the tree? tried to `return ::`->( arg )' but didn't seem to work.. </side-issue> (sorry for lengthy log, not sure what information is relevant and not...) DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/Proxy.pike:10:Error looking up 'ServerObject' in module '.'. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod.0:-: Warning: Compilation failed: Cannot call functions in unfinished objects. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod.0:-: Warning: Compilation failed: Cannot call functions in unfinished objects. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod.0:-: Warning: Compilation failed: Cannot call functions in unfinished objects. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod.0:-: Warning: Compilation failed: Cannot call functions in unfinished objects. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod.0:-: Warning: Compilation failed: Cannot call functions in unfinished objects. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod.0:-: Warning: Compilation failed: Cannot call functions in unfinished objects. Cannot call functions in unfinished objects. Unknown program: __empty_program() -> function("ServerObject") /home/kaos/pike/7.6.25/lib/master.pike:1399: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->ind("ServerObject") /home/kaos/pike/7.6.25/lib/master.pike:1436: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->`[]("ServerObject") /home/kaos/pike/7.6.25/lib/master.pike:1586: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod") }))->ind("ServerObject") /home/kaos/pike/7.6.25/lib/master.pike:1624: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod") }))->`[]("ServerObject") /home/kaos/pike/7.6.25/lib/master.pike:349: master()->compile_string("//$Id: Proxy.pike 168 2004-12-17 19:58:59Z kaos $\r\n\r\n#include <dls.h>\r\n\r\n//inhe"+[4969],"/home/kaos/ dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.p"+[15],0,DLS.Lib.RemoteObjectModel.Proxy,0,0) /home/kaos/pike/7.6.25/lib/master.pike:819: master()->low_findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/Proxy",".pike",0,0) /home/kaos/pike/7.6.25/lib/master.pike:928: master()->findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/Proxy",".pike",0,0) /home/kaos/pike/7.6.25/lib/master.pike:964: master()->low_cast_to_program("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/Proxy",0,0,0) /home/kaos/pike/7.6.25/lib/master.pike:1355: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->low_ind("Proxy",0) /home/kaos/pike/7.6.25/lib/master.pike:1412: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->ind("Proxy") /home/kaos/pike/7.6.25/lib/master.pike:1436: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->`[]("Proxy") /home/kaos/pike/7.6.25/lib/master.pike:1586: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod") }))->ind("Proxy") /home/kaos/pike/7.6.25/lib/master.pike:1624: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod") }))->`[]("Proxy") /home/kaos/pike/7.6.25/lib/master.pike:349: master()->compile_string("//$Id: module.pmod 168 2004-12-17 19:58:59Z kaos $\r\n\r\n#include <dls.h>\r\n\r\ni"+[10942],"/home/kaos/dev /dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectMod"+[20],0,object_program(DLS.Lib.RemoteObjectModel),,,1) /home/kaos/pike/7.6.25/lib/master.pike:819: master()->low_findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/module.pmod","",0,1) /home/kaos/pike/7.6.25/lib/master.pike:933: master()->findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/module.pmod",".pmod",0,1) /home/kaos/pike/7.6.25/lib/master.pike:964: master()->low_cast_to_program("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/module",0,0,1) /home/kaos/pike/7.6.25/lib/master.pike:1144: master()->low_cast_to_object("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/module.pmod",0,0) /home/kaos/pike/7.6.25/lib/master.pike:1342: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->low_ind("module",1) /home/kaos/pike/7.6.25/lib/master.pike:1270: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->module_checker()->`!() /home/kaos/pike/7.6.25/lib/master.pike:1410: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->ind("initialize") /home/kaos/pike/7.6.25/lib/master.pike:1436: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod")->`[]("initialize") /home/kaos/pike/7.6.25/lib/master.pike:1586: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod") }))->ind("initialize") /home/kaos/pike/7.6.25/lib/master.pike:1624: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/RemoteObjectModel.pmod") }))->`[]("initialize") /home/kaos/pike/7.6.25/lib/master.pike:349: master()->compile_string("//$Id: Application.pmod 168 2004-12-17 19:58:59Z kaos $\r\n\r\n#include <dls.h>\r\n\r\ninh"+[3590],"/home/ka os/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/Application.pmod",0,object_program(DLS.Lib.Application),,,1) /home/kaos/pike/7.6.25/lib/master.pike:819: master()->low_findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/Application.pmod","",0,1) /home/kaos/pike/7.6.25/lib/master.pike:933: master()->findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/Application.pmod",".pmod",0,1) /home/kaos/pike/7.6.25/lib/master.pike:964: master()->low_cast_to_program("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/Application",0,0,1) /home/kaos/pike/7.6.25/lib/master.pike:1144: master()->low_cast_to_object("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod/Application.pmod",0,0) /home/kaos/pike/7.6.25/lib/master.pike:1342: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod")->low_ind("Application",0) /home/kaos/pike/7.6.25/lib/master.pike:1412: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod")->ind("Application") /home/kaos/pike/7.6.25/lib/master.pike:1436: master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod")->`[]("Application") /home/kaos/pike/7.6.25/lib/master.pike:1586: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod") }))->ind("Application") /home/kaos/pike/7.6.25/lib/master.pike:1624: master()->joinnode(({ /* 1 element */ master()->dirnode("/home/kaos/dev/dls/branches/kaos-work/src/DLS.pmod/Lib.pmod") }))->`[]("Application") /home/kaos/pike/7.6.25/lib/master.pike:349: master()->compile_string("#!/usr/bin/env pike\r\n\r\n//$Id: DLS_boot.pike 161 2004-12-15 13:22:40Z kaos $\r\n\r\n// start new process running DLS module\r\nvoid spa"+[2580],"/home/kaos/dev/dls/branches/kaos-work/src/DLS_boot.pike",0,DLS_boot,0,0) /home/kaos/pike/7.6.25/lib/master.pike:819: master()->low_findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS_boot",".pike",0,0) /home/kaos/pike/7.6.25/lib/master.pike:934: master()->findprog("/home/kaos/dev/dls/branches/kaos-work/src/DLS_boot","",0,0) /home/kaos/pike/7.6.25/lib/master.pike:964: master()->low_cast_to_program("/home/kaos/dev/dls/branches/kaos-work/src/DLS_boot","/home/kaos/pike/7.6.25/lib/master.pike",0,0) /home/kaos/pike/7.6.25/lib/master.pike:998: master()->cast_to_program("/home/kaos/dev/dls/branches/kaos-work/src/DLS_boot","/home/kaos/pike/7.6.25/lib/master.pike",0) DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/Proxy.pike:10:Illegal program pointer. DLS.pmod/Lib.pmod/RemoteObjectModel.pmod/module.pmod:291:Error looking up 'Proxy' in module '.'. DLS.pmod/Lib.pmod/Application.pmod:66:Index 'initialize' not present in module 'RemoteObjectModel'. DLS.pmod/Lib.pmod/Application.pmod:67:Index 'init_ok' not present in module 'RemoteObjectModel'. DLS.pmod/Lib.pmod/Application.pmod:67:Index 'no_server' not present in module 'RemoteObjectModel'. DLS_boot.pike:88:Placeholder already has storage! DLS_boot.pike:88:Error looking up 'Application' in module 'Lib'. Pike: Failed to compile script: Compilation failed. /home/kaos/pike/7.6.25/lib/master.pike:2650: master()->_main(({"kpike","-DDEBUG","DLS_boot"}),({"MANPATH=/usr/share/man:/usr/local/share/man:/usr/share/gcc-data/i686-pc-linux-gnu/ 3.3/man:/usr/X11R6/man::/opt/blackdown-jdk-1.4.2.01/man:/usr/qt/3/doc/man",,,45}))

6 20

RES: Bare-bones Pike
by Mirar ＠ Pike developers forum 28 Dec '04

28 Dec '04

I think it's solved already, yes.

1 0

RES: Bare-bones Pike
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 28 Dec '04

28 Dec '04

That may just be a very good (read "easy") way of getting around the problem. I would very much like to hear what Grubba and mast has to say about that solution. If they approve, I'll go ahead and write a small wrapper lib..

2 2

RES: Bare-bones Pike
by Mirar ＠ Pike developers forum 28 Dec '04

28 Dec '04

I haven't really looked into it, but shouldn't it be possible to use a library with few symbols that use the dynamic library loader to load the rest of the pike, and thus doesn't share the symbols? Just as Pike loads .so modules. [adding dev] / Mirar Previous text: >12737290 2004-12-28 08:48 /10 lines/ Marcus Agehall (PacketFront) >Recipients: Pike (-) importmöte för mailinglistan >Comment to 12735984 >Subject: RES: Bare-bones Pike >-------------------------------------------------------------------- >I've done some work on embedding pike. Currently, there isn't much >going on on that front. > >Basically, to embed pike, you must change the main routine a bit. I >have those changes somewhere and I should probably commit them to the >7.7 repository... > >Anyway, the biggest problem with embedding pike, is that you get a >*LOT* of symbols with the lib. This can cause you problems, but if you >manage to avoid name clashes, you should be fine. > >(12737290) /Marcus Agehall (PacketFront)/--------------------------- >

1 0

Re: [Chilimoon-dev] ChiliMoon source repository migration to SVN/SVK?
by Stephen R. van den Berg 25 Dec '04

25 Dec '04

Johan Sundstr?m (Achtung Liebe!) @ ChiliMoon (-) Mooh, mooh wrote: >> One final question here; would anybody object to actually picking my >> current SVN/SVK repository as master for the ChiliMoon sources? >I think that would be great. If and when the time comes for migrating Ok, I'm setting up things now then. If anybody objects, he'd better hurry :-). >UI, it might be worth testing some alternative; the demos I've seen of >Chora for instance (http://freshmeat.net/projects/chora/), isn't tenth >as bad as ViewCVS. Quite so. I'll leave this as an exercise to the reader for now. Especially since you can mirror the SVK repository and test it locally (without going over the Internet). >Besides, actually having a live svn repository might encourage people >to upgrade code librarian all the way to supporting subversion. (Not >sure if I'll have the time myself, but it's more likely than if there >is no present need for it.) Quite right. It never hurts to tickle some interest. >The same probably applies to the Pike site and repository, eventually. >Will there be a read-only subversion tree open for Pike, that we can >point to from the site (noting details such as how often it is synced >et cetera)? I'm making read-only versions of Pike and Roxen available; synced at least every night, possibly even every hour (I have to check what kind of load it creates). The nice thing about the Roxen SVN I'm making available is that it is completely linked with the ChiliMoon repository. ChiliMoon will be read-only for all, and read-write only for developers, of course. -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). Are they twins? Yes. Are they *both* yours? _______________________________________________ Chilimoon-dev mailing list Chilimoon-dev(a)list.chilimoon.org http://pipermail.gusi.at/mailman/listinfo/chilimoon-dev

1 0

ChiliMoon source repository migration to SVN/SVK?
by Stephen R. van den Berg 25 Dec '04

25 Dec '04

I'm almost done with the migration and integration of the various source repositories. One final question here; would anybody object to actually picking my current SVN/SVK repository as master for the ChiliMoon sources? We lose the nice graphical interface which is on the current repository on lysator. I could start exporting my repository to that CVS. OTOH, there exist similar interfaces for SVN. Alternately, by using SVK, you have your own local copy of everything which works *really* fast and easy (much better than plain SVN). I can give write access to all ChiliMoon developers here. I don't mind (might even encourage) moving the repository back to lysator (now or later). Incidentally, this also means that I have a fully SVN/SVK up-to-date mirror for both Roxen and Pike repositories. If someone wants the repository in order to migrate Roxen and/or Pike to SVN, just drop me a note. And, yes, this also means that I have retrofitted SVN/SVK to fully show that ChiliMoon emerged out of Roxen around 2002/06/03 and that they share the same repository history now (file moves and renames and everything). As soon as we agree on where the ChiliMoon repository lives, I'll hand out coordinates to access it (we have enough bandwidth here to host it for now, if that is what we would decide on). P.S. Merry Christmas everyone :-). -- Sincerely, srb(a)cuci.nl Stephen R. van den Berg (AKA BuGless). Are they twins? Yes. Are they *both* yours?

2 1

encode_value? decompile pike programs?
by Martin Bähr 24 Dec '04

24 Dec '04

hi, many many years a go there used to be a way to turn an array or mapping into a readable string that later could be turned into an array/mapping again. i believe that back then the functions encode_value() and decode_value() were used for this. now these functions use some unreadable binary format. what ways are there available today to achive something similar? sprintf("%O") may be used for encoding, but the result contains newlines and comments which i'd rather not have included. is it possible to make sprintf("%O") produce something more compact? on a related note i wonder how it could be achived to "decompile" a program or object. ie. have pike create the source necessary to recreate a value. greetings, martin.

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