Pike-devel June 2008

pike-devel@lists.lysator.liu.se

9 participants
20 discussions

7.8 blockers
by Peter Bortas ＠ Pike developers forum 15 Aug '08

15 Aug '08

7.8 blockers: Owner Issue [/] Fallback to poll from epoll (from the conference road map). Implemented, but further testing is needed, as well as updated documentation. [ ] Fix gc of Stdio.File (from the conference road map). [ ] mast/zino New Windows build environment. [ ] per/marcus Performance regression --with-assembler. (per and marcus weren't present so item assigned without consent... per says memprotect() is responsible as far as -x benchmark goes.) [ ] zino/mast Building external modules should work. [ ] nilsson Write ChangeLog. [/] Module dumping should succeed for all modules. Currently it succeeds for all modules but 3: [ ] Tools.Standalone.dump [ ] Local [ ] Locale Non-blockers: [ ] jhs Build (SVG) graph from the -x benchmark results Pikefarm delivers to track development. [ ] An API for safely creating temporary files. Possibly wrapping mkstemp/mkdtemp. If you think you could help with any of the items please do. Especially the items that have no one assigned to them yet.

9 81

Process.run
by Peter Bortas (nu med mindre Opera) ＠ Pike (-) developers forum 15 Jul '08

15 Jul '08

I just checked in a Process.run() in 7.7: http://pike.ida.liu.se/development/cvs/diff.xml?module=Pike&file=7.7/lib/mo… The rational for that is that I was once again reminded by a user this week that getting Process.create_process() or Process.Process right without some corner case blocking is hard. It's not obvious that if you bind pipes to booth stderr and stdout you have to take in to account that OS buffers are not limetless. Process.run() is a thin wrapper around Process.Process that collects stdout, stderr and exitcode and return them in a mapping. This could potentially result in huge strings, but will do what most users want and even already do when they call create_process() with both pipes bound. Something like this should be in 7.8, but I'm open to suggestions for other things that might be usefull to return in the mapping or for changing member names.

5 7

comments on "simplified method for external modules"
by Bill Welliver 01 Jul '08

01 Jul '08

I've been following the changes file and just thought I would mention that the subject example includes GNU-makeisms that aren't compatible with standard make. Also, is it appropriate to recommend that users not use the standard module build method? The sample, while simple, seems to require the inclusion of a lot of rules that already exist in dynamic_module_makefile, however without a lot of the edge case handling. I'm all for simplification, but I'm concerned that recommending users write modules in this manner will result in a lot of modules floating around that don't build or install properly. Bill

4 6

Mapping generations
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 27 Jun '08

27 Jun '08

Mappings got generation counters yesterday. Although the overhead is fairly small (poking a flag on every change, and added storage in each mapping_data for a 32 bit counter), so is the utility; it at least deserves some discussion whether it should be there or not. Aside from that, I got a couple of remarks on the implementation: o The new builtin function m_generation isn't critical enough to deserve a place on the global level imho. o If this is the way to go, it's not far fetched that generation counters will be added to the other data types too. Thus the names "m_generation" and "_m_generation" (for the lfun) aren't generic enough. Simply "generation" and "_generation" seems better.

8 14

7.8 wrap up weekend
by Peter Bortas ＠ Pike developers forum 27 Jun '08

27 Jun '08

On the weekend of 27-29/6 we plan to resolve the remaining issues with 7.8. Some of us will meet in person, some will communicate over KOM. You are encourage to participate virtually even if your preferred medium of communication is IRC or other IM-systems.

7 15

Pike/Roxen: clean start issue
by cschalkwijk 24 Jun '08

24 Jun '08

I've got a module.pmod acting as a static class for some modules. In this class there is an error, but it didn't show up until I made another error in the same class (with newly added code) This means I've been using _some_ version of my module.pmod other than I was expecting. This is very, very strange and frustrating. Even more, when you take into account that I regularly start/stop roxen, using the startup script, killall ... and killall -9 ..., roxen is started with the --remove-dumped option, and the error even went by unnoticed after a full system (cold) reboot, which left the machine down for at least 48 hours. Did pike or Roxen not notice the error or was the code not used at all? Greetings, Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

3 5

Xenoclient: default config for 7.6 and 7.7
by bertrand.lupart＠linkeo.com 23 Jun '08

23 Jun '08

Hello, The default config for the xenoclient available to download here: http://pike.ida.liu.se/development/pikefarm/ http://pike.ida.liu.se/projects/pikefarm/clientdists/xenoclient-1.2.tar. gz contains a default config for 7.4 and 7.5 which obviously fails. It would be nice to have a xenoclient with defaults to 7.4, 7.6 and 7.7. One is available here: http://bertrand.lupart.free.fr/xenoclient-1.2.1.tar.gz ----8<----8<----8<----8<---- $ diff -ruN xenoclient-1.2 xenoclient-1.2.1 diff -ruN xenoclient-1.2/config/pike7.5.cfg xenoclient-1.2.1/config/pike7.5.cfg --- xenoclient-1.2/config/pike7.5.cfg 2003-01-23 01:14:51.000000000 +0100 +++ xenoclient-1.2.1/config/pike7.5.cfg 1970-01-01 01:00:00.000000000 +0100 @@ -1,10 +0,0 @@ -configformat: 2 -project: Pike -projectdir: pike-7.5 -snapshoturl: http://pike.ida.liu.se/generated/pikefarm/packages/7.5/latest -resulturl: http://pike.ida.liu.se/generated/pikefarm/packages/7.5/result -test: default make xenofarm -#test: dmalloc make xenofarm CONFIGUREARGS="--with-dmalloc" -#test: feature make xenofarm_feature -#test: thorough make xenofarm_feature CONFIGUREARGS="--with-dmalloc" -#test: static make xenofarm CONFIGUREARGS="--without-dynamic-modules" diff -ruN xenoclient-1.2/config/pike7.6.cfg xenoclient-1.2.1/config/pike7.6.cfg --- xenoclient-1.2/config/pike7.6.cfg 1970-01-01 01:00:00.000000000 +0100 +++ xenoclient-1.2.1/config/pike7.6.cfg 2008-06-20 11:10:23.000000000 +0200 @@ -0,0 +1,10 @@ +configformat: 2 +project: Pike +projectdir: pike-7.6 +snapshoturl: http://pike.ida.liu.se/generated/pikefarm/packages/7.6/latest +resulturl: http://pike.ida.liu.se/generated/pikefarm/packages/7.6/result +test: default make xenofarm +#test: dmalloc make xenofarm CONFIGUREARGS="--with-dmalloc" +#test: feature make xenofarm_feature +#test: thorough make xenofarm_feature CONFIGUREARGS="--with-dmalloc" +#test: static make xenofarm CONFIGUREARGS="--without-dynamic-modules" diff -ruN xenoclient-1.2/config/pike7.7.cfg xenoclient-1.2.1/config/pike7.7.cfg --- xenoclient-1.2/config/pike7.7.cfg 1970-01-01 01:00:00.000000000 +0100 +++ xenoclient-1.2.1/config/pike7.7.cfg 2008-06-20 11:10:46.000000000 +0200 @@ -0,0 +1,10 @@ +configformat: 2 +project: Pike +projectdir: pike-7.7 +snapshoturl: http://pike.ida.liu.se/generated/pikefarm/packages/7.7/latest +resulturl: http://pike.ida.liu.se/generated/pikefarm/packages/7.7/result +test: default make xenofarm +#test: dmalloc make xenofarm CONFIGUREARGS="--with-dmalloc" +#test: feature make xenofarm_feature +#test: thorough make xenofarm_feature CONFIGUREARGS="--with-dmalloc" +#test: static make xenofarm CONFIGUREARGS="--without-dynamic-modules" ---->8---->8---->8---->8---- -- Bertrand LUPART http://bertrand.gotpike.org/

1 0

Building standard modules
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 18 Jun '08

18 Jun '08

Where a module provides a single feature, and that feature is disabled (./configure --without-foo), the DSO is still produced, but without (meaningful) code. Would it be much work to change this so that no such dummy modules would be built? Furthermore, if a feature is requested but the configure script can't find the required headers or libraries, the sole effect is to disable the feature. Although it's possible to programatically check what features have actually been built, I think it would be better if the build would fail in case of problems, or if at least the corresponding files would not be produced.

1 0

Perl
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 17 Jun '08

17 Jun '08

The Perl module has been dropped from Pike 7.7. Was it because it felt silly, because noone used it, or some other reason?

2 2

FreeBSD port maintainership drop
by Xavier Beaudouin 17 Jun '08

17 Jun '08

Hello, Sorry for the broadcast... I am currently the maintainer of lang/pike7* ports. I no longer use them nor getting time to maintain them. If someone has time and patience, please feel free to tell me. Sincerly, /Xavier

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 June 2008