Pike-devel December 2007

pike-devel@lists.lysator.liu.se

3 participants
9 discussions

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

Getopt mark II
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 19 Apr '08

19 Apr '08

(or rather Getopt mark III, since I've already rewritten the current one, although no functionality was changed then) I've been working a bit on a new Argument parser, and would like some input. In reality there will be two different way of using the argument parser, which really doesn't share any code but is convenient to do at the same time. The first one is a "I just want to get this over with" kind of interface: void main(int num, array argv) { mapping args = Arg.parse(argv); argv = args[Arg.REST]; } The output will contain ([ "foo":1 ]) if the argument is --foo and ([ "foo":"bar" ]) if the argument is --foo=bar. There is no fancy stuff to handle default values (just or it with another mapping) or options that may or may not have values (e.g. -bar=foo will produce ([ "b":1, "a":1, "r":"foo" ]) and --foo x --bar will just produce ([ "foo":1 ]) and then stop processing the line). The other mode is the (supposedly) easy yet powerful mode that you would use for more mature applications. class Parser { inherit Arg.Options; Arg verbose = NoArg("-v")|NoArg("--verbose")|Env("VERBOSE"); Arg level = HasArg("-l")|HasArg("--level"); } void main(int n, array argv) { Parser p = Parser(argv); // Index magic. Some like it, some not so much. if( p->verbose ) werror("Level %s\n", p->level); } Which is extended in class Parser { // The name for now. inherit Arg.OptionsSupreme; Arg verbose = NoArg("-v")|NoArg("--verbose")|Env("VERBOSE"); // These are used in the automatically generated --help response. string help_pre = "This program is like awesum."; string verbose_help = "Increases the verbosity of the program."; // Called when/if verbose is set to a value. void verbose_cb(string arg) { werror("Verbosity is on.\n"); } } Does this match the long list of requirements that I've heard from others?

5 17

pike-svn repo import into git
by Martin Bähr 23 Feb '08

23 Feb '08

hi, importing the pike-svn repo into git took 3 days. git-svn seems to have some issues there, as the process got slower and slower (and in the end git-svn had more than 300MB in ram (allocated 1GB)) the resulting repo had 178645 objects and a size of 1178MB. git-svn allocates another 1.5GB for statusinformation on each branch. (and because tags are branches, the 1729 tags result in as many branches) however, after packing, the resulting repo ocupies a mere 44MB!!! that alone is a good reason for me to use git, as it it gives me the whole repo in the same space as the checkout of a single revision in svn. you can clone this repo from http://www.iaeste.at/~mbaehr/pike-svn.git the svn import info is removed from that repo. when we switch to svn i'll try to make a repo available that contains the svn info to spare anyone else who wants ot use git-svn a 3day import. greetings, martin.

5 9

debian package of pike (and caudium)
by Henrik Andreasson 23 Feb '08

23 Feb '08

Hi! How is it going with the debian packages of pike, anything I can to to help? The package is still owned by debian-qa-team maybe a new version that adopts the package would be good? Shamless request: I'm going to take over the caudium package but I'm not yet a debian developer so maybe somebody on the list could help me in the beginning with the uploads? //Henrik Andreasson "kinneh"

8 9

7.6 release plans?
by H. William Welliver III 07 Jan '08

07 Jan '08

Hi All, I was wondering if there were any plans to do a new 7.6 release in the near future. There's a bug that's critical for me in the .112 Mysql module that causes a segfault, that's been fixed in 7.6 CVS. Because of this, I was thinking about holding off on a release on my end if a new pike version was looming on the horizon. If not, that's okay, too, I can try to come up with a workaround. Bill

4 8

Assumed .pike
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 28 Dec '07

28 Dec '07

If .pike is omitted when declaring a script to run, Pike will add this automatically. It will however not update the argv array. Is this the behaviour you would expect? Example. foo.pike: void main(int n, array args) { write("%O\n", args); } $ pike foo bar ({ /* 2 elements */ "/home/nilsson/foo", "bar" })

3 2

pcre bundled with pike 7.8
by H. William Welliver III 20 Dec '07

20 Dec '07

I'm not sure if this was discussed previously, but would there be any possibility of bundling pcre with pike 7.8, or at least compiling with it on windows? Just wondering... bill

3 7

external module building under 7.7
by H. William Welliver III 15 Dec '07

15 Dec '07

I've been playing around with external module building under Pike 7.7, and I think that most of the difficulty involves propagated_variables. There's a propagated_variables file that gets installed in include/pike, but it seems that the macro that actually reads this file only looks for it in the current directory. I think I understand that rationale when compiling within the source tree, but think there needs to be a behavior that checks for the file in the installed headers directory too. The question for those more knowledgeable in this magic is: does it seem reasonable to check in the installed headers directory first (most likely $BUILD_BASE, I think), then in the current directory for all situations or would that have an undesirable effect when compiling within the Pike source tree?

3 2

pike on iphone
by H. William Welliver III 01 Dec '07

01 Dec '07

I've been playing around with the idea of getting pike to run on apple embedded devices. I don't have an iphone, but I do have an ipod touch, which is essentially the same thing. I managed to get gmp and nettle to compile, but without assembler. It's not clear at this point whether the problem is due to incorrect detection of the assembly type, or some other problem. Pike's configure script seems to run correctly, but my current problem is that the current iphone toolchain uses LLVM-GCC, which is pretty buggy, and it crashes while compiling multiset.c. I'm not sure whether I want to go through the effort of trying to fix that problem or if using straight gcc would work better (assuming that gcc generates arm objects for darwin). Anyhow, I thought that some out there might be interested in this. Bill

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 2007