Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

syntax reference and other docs
by Martin Baehr 21 Oct '03

21 Oct '03

hi, when trying to look something up about pike syntax it occured to me that there is no syntax reference. the chapturized reference manual has some of it, but where do i eg find a complete(!) description of eg inherit. ? just like the module reference a reference for all keywords would be nice. besides that, the titles module tree quick reference and complete chapterized reference manual are a bit confusing. the module tree reference isn't exactly quick but rather complete nowadays, while the features of pike have surpassed the chapterized manual making it incomplete. i'd suggest to change the titles to: module tree complete reference, and chapterized reference manual.

3 3

Pike Conference 2003 - mp3
by Martin Baehr 21 Oct '03

21 Oct '03

hi, i am starting to work through the recordings and make them presentable, the first day is now available on http://steam.upb.de/conferences/pike2003/timetable.xml for your listening pleasure. more will follow as i find time. slides for the presentations will be made available as well. (if you still have slides that you didn't yet upload, now might be a good time. if you need help don't hesitate to contact me) being new to this audio manipulation, i welcome any tipps and trick you might have to help clear up some of the parts. greetings, martin. -- interested in doing pike programming, sTeam/caudium/pike/roxen training, sTeam/caudium/roxen and/or unix system administration anywhere in the world. -- pike programmer working and travelling in europe open-steam.org unix system- bahai.or.at iaeste.(tuwien.ac|or).at administrator (stuts|black.linux-m68k).org is.(schon.org|root.at) Martin Bähr http://www.iaeste.or.at/~mbaehr/

1 0

-= failure
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 20 Oct '03

20 Oct '03

I just stumbled upon > object a=Image.Image(1,1); > array b = ({ a, "foo" }); > b -= ({ a }); `==: illegal argument 2 ___Image.image: Image.Image( 1 x 1 /* 0.0Kb */)->`<("foo") HilfeInput:1: HilfeInput()->___HilfeWrapper() Would it be useful with a fallback that ignores overloading whims and looks at the svalues (and thus effectively hides these errors)?

2 3

putenv/getenv
by Bill Welliver 19 Oct '03

19 Oct '03

I've cobbled together a System.putenv() and System.getenv(), but I'm having some odd problems. The code itself works most of the time, but randomly getenv() fails to get an envvar I've putenv()ed (ie getenv(2) returns NULL). The functions are below, along with a short test script that demonstrates the problem. Any suggestions are welcome, as my C skills are quite rusty. Bill in modules/system/system.c: #include <stdlib.h> static void f_system_putenv(INT32 args) { int rv; char *envvar; get_all_args("putenv", args, "%s", &envvar); pop_n_elems(args); rv=putenv(envvar); push_int(rv); } static void f_system_getenv(INT32 args) { char *rv; char *envvar; get_all_args("getenv", args, "%s", &envvar); pop_n_elems(args); rv=getenv(envvar); if(rv==NULL) push_int(0); else push_text(rv); } and later: ADD_FUNCTION("putenv", f_system_putenv, tFunc(tStr, tInt), 0); ADD_FUNCTION("getenv", f_system_getenv, tFunc(tStr, tOr(tStr, tInt)), 0); test script: int fail=0; int main() { string var="DISPLAY"; string val="BASE"; int a='A'; for(int i=0; i<2050; i++) { val+=String.int2char(a); werror("iteration " + i + "\n"); doit(var,val); } werror("failures: " + fail + "\n"); return 1; } void doit(string var, string val) { if(System.putenv(var+"="+ val)) werror("failed putenv\n"); string r=System.getenv(var); if(r!=val) { fail++; } The test fails consistently and in the same locations for a given environment variable. The manpage doesn't say what might cause failures like this. Any thoughts? Bill

9 28

steps needed to get the module repository up and running
by Martin Baehr 18 Oct '03

18 Oct '03

so far we have been discussing things that pike needs to handle a module repository, how we want the repository organized, but we have not yet looked at the steps needed to get the ball rolling. some of these things already exist, but if so then all the better: first: * we need a server where people can upload their files. * a place where they can register for an account. * a place where they can announce their module. (this should ask questions like the desired class name) * integration of these into the pike site. then: it should be possible to browse the class hierarchy to download classes and read docs at the same time. both should be available by simple memorizable urls like: http://pike.ida.liu.se/classes/Protocols/LMTP/Server/ (this would also be nice for the docs themselves. ie: generated/manual/modref/ex/predef_3A_3A could be linked to something short) i believe the fixes to the module build process are not a prerequisite for this part here. they can be done in paralell or even after this. does the pike site have everything we need? should we have another site? do we have volunteers to set it up? greetings, martin.

8 15

more module repository ramblings
by Bill Welliver 17 Oct '03

17 Oct '03

Another thought I had was that I think that it should be possible for the repository to hold modules for both well known places in the tree (such as Protocols.HTTP.*) as well as a sort of Public area (such as the PRAWN.* namespace :)). Modules that want to get into a well known location would have to jump through more hoops, from both a sanity and quality perspective. There'd be less control over the Public location, and you'd basically be able to get a whole subtree such as PRAWN.Protocols.BillsJabberClient or PRAWN.Parser.PigLatin. Any thoughts? Bill

6 11

Strange things with Stdio.File
by David Gourdelier 17 Oct '03

17 Oct '03

Hi list, I am have some problems with Stdio.File which looks quite the same telling about the attempt to call the NULL-value when using non blocking I/O: Attempt to call the NULL-value Unknown program: 0(0,"* OK [CAPABILITY IMAP4rev1 CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT] Courier-IMAP ready. Copyright 1998-2003 Double Precision, Inc. See COPYING for distribution informatio"+[5]) /usr/local/pike/7.2.512/lib/modules/Stdio.pmod/module.pmod:692: Stdio.File("socket", "localhost:143", 777 /* fd=-1 */)->__stdio_read_callback() Attempt to call the NULL-value Unknown program: 0(0,"421 Error: timeout exceeded\r\n") /usr/lib/pike/7.2.526/lib/modules/Stdio.pmod/module.pmod:692: Stdio.File("socket", "127.0.0.1:10026", 777 /* fd=35 */)->__stdio_read_callback() Do you know what these mean ? FYI I use Pike 7.2.512 and 7.2.526. / David Gourdelier

2 3

module repository ramblings
by Bill Welliver 16 Oct '03

16 Oct '03

I've taken a few minutes to jot down some ramblings concerning a Pike module repository. I know that there was a proposal a while back called PUMA, though I can't find any trace of it when I went to look for it. I'm sure that it has some very good ideas that I will have neglected to include here. If that's the case, or if you have any thoughts, please feel free to send them my way. * Initial tasks that need to be accomplished 1. The build/install system should be updated for the various varieties of modules: Modules with C component (ok) Modules with C and one Pike (ok, but see the problem below) Modules with C and multiple Pike Modules with Pike (see the problem below) Modules with multiple Pike 2. Skeleton modules should be prepared for the various varieties of modules. 3. The documentation build tools should be modified to allow partial merging of new documentation. The extracted documentation should be installed to facilitate the documentation process. 4. A local install option should be added so that a user may install a module in their local module tree. 5. A method for passing arguments to the configure process should be developed. * A Practical Problem When someone is granted a spot in the namespace, what are they getting? do they get the whole subtree below where they've been granted? Example: if I get Protocols.NNTP, for the purposes of making a client, can anyone else get their module in that tree or do they have to look somewhere else? I worry that we'd end up with essentially a 2 level module tree. Also, this problem manifests itself in the handling of the installed modules and how to make room for others. If a module is installed like this (example Protocols.NNTP): lib/modules/Protocols.pmod/NNTP.pmod (single pike file) how do we handle someone wanting to create Protocols.NNTP.Server? would it be better to have all modules installed as module.pmod within ModName.pmod direcories? This would give the maximum amount of flexibility as far as making room for other modules to be slid in, but really seems inefficient, in that we'd most likely only have one module file per directory. * Namespace Management Coordination of the namespace will be handled by a namespace management board ("the Board"). The board should be made up of not less than 3 developers. The board should reflect the makeup of the Pike user community, with representatives from the IDA team, core developers and non-core developers. Q: Should there be requirements for membership and/or rotating positions? The Board is responsible for the smooth operation of the repository, and for keeping the namespace manageable. The Board is the final authority for handling namespace issues that may arise among developers. When practical, the Board should attempt to obtain consensus among its members when making decisions. The Board may delegate responsibility for a given branch of the module naming tree to a non-Board member, though the Board will always retain the right to assert control over delegated branches. Coordinators of delegated branches must remain active in thier role. If such a developer is no longer able to perform the duties of a branch coordinator, they must return control of the branch to the Board. All coordinators should be contacted on a regular basis (several times per year) to verify that they are accessible and able to carry out these duties. * Duties of coordinators might include: a) granting positions in the tree to other module developers b) assisting module developers in making wise decisions concerning module and class naming c) making sure that modules in their respective section of the repository comply with the requirements for inclusion (quality control) * Adding modules to the repository Before a module can be contributed to the repository, the module's author must request a place for that module within the module namespace. The request should include at least the following: a) Developer Name b) Contact Information (at least email, but potentially other means) c) Proposed module location in the namespace d) Estimated scope of namespace usage (subclasses and possibility of other modules beneath) e) Request for coordination (if the tree is not already delegated) Ideally, the process for making requests and having the requests approved would be streamlined and part of a semi-automated workflow. * Requirements for modules in the repository All modules must meet the following requirements (quality control): a) Author name and contact information must be provided b) License must be clearly declared c) Version of the module must be included as a constant in the module d) API Documentation (should be provided), and must be in autodoc format e) Modules must use the standardized build and installation interfaces f) Modules must not cause interference with other modules in the tree A directory of information about modules in the repository will be maintained by the Board. This directory should contain information about modules, their function, changes and versions, compatibility and dependency information. A distributed network of nodes will make the directory and the modules themselves available for access by users. The directory will also be used to provide a web service that will allow a user to locate, download and install modules automatically. Well, that's about all I have for now. Please give me your thoughts, flames and other assorted musings. Bill

10 16

GTK.FileSelection incorrect refdoc
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 16 Oct '03

16 Oct '03

hi! I've found a bug in the refdoc for GTK.FileSelection the doc says: get_ok_button() get_cancel_button() get_help_button() indices on a FileSelection object says: ok_button() help_button() cancel_button() withou the get best regards thomas

1 0

valgrind
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 16 Oct '03

16 Oct '03

Ok, a new snapshot of valgrind is out, which finds new problems. I won't look further at this problem (threads are a non-expertise area for me), so if someone has free time to identify/fix the problem, be my guest. Doing tests in tlib/modules/testsuite (319 tests) test 314, line 732 sched status: Thread 1: status = WaitCV, associated_mx = 0x8338630, associated_cv = 0x4214F98C ==17679== at 0x4028CE47: pthread_cond_wait (vg_libpthread.c:1095) ==17679== by 0x815E4C4: f_thread_create (/home/nilsson/Pike/7.5/src/threads.c:937) ==17679== by 0x808079E: low_mega_apply (/home/nilsson/Pike/7.5/src/apply_low.h:210) ==17679== by 0x8082B49: mega_apply (/home/nilsson/Pike/7.5/src/interpret.c:1844) ==17679== Warning: pthread scheduler exited due to deadlock

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