Pike-devel October 2003

pike-devel@lists.lysator.liu.se

11 participants
58 discussions

Pike Interpreter Lock
by fomyers＠netwalk.com 21 Oct '03

21 Oct '03

Hi, For integrity, The garbage collection process requires that the Pike global interpreter lock be held. This implies that all threads hold this lock in their turn while executing. Is this a single (intra-)Process lock, or a cross (inter-) Process lock. To put the question another way, does the lock span process boundries, or just threads within a Pike Process? Will this locking single-thread Pike execution in a Multi-Process environment? Frank

2 1

My_Backend and Select
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 21 Oct '03

21 Oct '03

No, sorry, I used "poll" in the wrong context. It uses poll(2) or select(2), so it will really wait in the timeout interval. It's only if you specify a time limit of 0.0 that you'll get a busy loop. / Martin Stjernholm, Roxen IS Previous text: >2003-10-21 21:20: >Subject: My_Backend and Select >-------------------------------------------------------------------- >Martin, > >I think I understand the process of adding a pike program object and running it >as a backend loop, but it's still a polling loop right? > >Isn't that a high overhead process? Isn't there a way to wait for activity on a >stream or other I/O Object? > >Frank > > > > / Brevbäraren >

1 0

Select via My_Backend()
by fomyers＠netwalk.com 21 Oct '03

21 Oct '03

Martin, Thank you for your prompt reply. I am confused by the reference to '() which (I believe) is "the function call operator callback". I would be calling an object method in a loop. This looks like polling which seems to be a resource heavy way to wait for signals related to the telnet objects. Are signals generated for telnet objects visable only within those objects? Is there an event wait implied within the '() call? Thanks for your time, and patience. Sincerely, Frank

1 0

(no subject)
by fomyers＠netwalk.com 21 Oct '03

21 Oct '03

Hi, I'm trying to write a single-threaded telnet server, but I am cannot find the equivalent of the C "int select(...)" function within Pike. Is this accomplished via sleep and signal checking, or am I missing something basic? I know that if I return -1 I enter the "event loop", but I'm looking for a way to "wait" for I/O signals for only the telcom I/O that I am managing in this code. Any hint would be appreciated. Thank you for you time, and patience. Sincerely, Frank

2 1

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 20 Oct '03

20 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 17 Oct '03

17 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

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 October 2003