Pike-devel March 2007

pike-devel@lists.lysator.liu.se

4 participants
17 discussions

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

14 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

error: `LIBS' was not set in the previous run
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 30 Jul '07

30 Jul '07

Has anyone else seen this problem? When building current 7.7 from scratch, it bombs out during the configuration of CommonLog: configure: loading cache ../.././config.cache configure: error: `LIBS' was not set in the previous run configure: error: changes in the environment can compromise the build In config.cache there is the following: ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= (these are the only ac_env/ac_cv_env entries). Maybe this is related to the line LIBS= in PIKE_RETAIN_VARIABLES somehow? Interestingly enough, the problem does not occur on my PS3, which also has ac_cv_env_LIBS_set= ac_cv_env_LIBS_value= in config.cache...

3 8

Returning 0 vs throwing errors in Stdio
by Peter Bortas ＠ Pike developers forum 27 Apr '07

27 Apr '07

I'd like someone to expand on the advantages of the following change in 7.7: > o Stdio > The functions read_file(), read_bytes(), write_file() and > append_file() now always throw errors upon errors, to allow easier > use as errno doesn't have to be checked. read_file() and > read_bytes() still returns 0 if the file does not exists. Specificly for read_file() on files you lack permissions for. > Stdio.read_file("/etc/shadow"); (1) Result: 0 vs > Stdio.read_file("/etc/shadow"); Failed to open "/etc/shadow": Permission denied /pkg/pike/intel-debian3_1/7.7.13/pike/7.7.13/lib/modules/Stdio.pmod/module.pmod:1820: Stdio->read_file("/etc/shadow",UNDEFINED,UNDEFINED) As I see it it only makes it harder to properly handle errors. If Pike had a well developed system for handling errors it would be an improvement, but now it's only going to lead to more and buggier code. Unless someone can come up with a good explanation* for why it should be changed it should be reverted. * Like for example "I've extended and documented the error classes. It's obvious and clear how to use them now!". That'd be nice.

7 16

New function call type checker for pike
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 01 Apr '07

01 Apr '07

Those who have monitored the Pike 7.7 CVS the last week or so, may have noticed a few new type checking related functions. These are intended to replace the current style of type checking where a function type for the current call is created and then compared in one pass against the declared type. This has led to somewhat cryptic error messages. eg: > `+((["":14]), "", 14); Compiler Error: 1:Bad argument 2 to `+. Compiler Error: 1:Expected: !function(!(object | mixed) ... : mixed) & function | function(int, int ... : int) | !function(!float ... : mixed) & function(int | float, int | float ... : float) | !function(!string ... : mixed) & function(string | int | float, string | int | float ... : string) | function((0=array), (1=array) ... : 0 | 1) | function((0=mapping), (1=mapping) ... : 0 | 1) | function((0=multiset), (1=multiset) ... : 0 | 1) Compiler Error: 1:Got : function(mapping(string(0):int(14..14)), string(0), int(14..14) : void | mixed) The new code is instead based on checking the arguments one at a time, but this means that the error in the above case is first detected when the last argument is checked: Compiler Error: 1:Bad argument 3 to `+, got int(14..14), expected object. This problem can be reduced by also adding warnings about prior arguments in case of the above error: Compiler Warning: 1:Potentially bad argument 2 to `+, got string(0), expected mapping | object. The question is what text the warning should have.

4 6

New function call type checker for pike
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 30 Mar '07

30 Mar '07

Hmm... Seems to work even for the more obscure cases: > typeof(class{}); (4) Result: function( : object(is HilfeInput()->__class_65709_0_line_1)) > typeof(Stdio.Stat()); (5) Result: object(is _static_modules.files()->Stat) Note that it will fall back to the old syntax if it fails to look up the program id: > _typeof(compile_string("")); (6) Result: function( : object(is 65723)) > mixed x = compile_string(""); > _typeof(x); (7) Result: function( : object(is -))

1 0

New function call type checker for pike
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 30 Mar '07

30 Mar '07

1 0

step and break opcodes
by H. William Welliver III 29 Mar '07

29 Mar '07

Can someone familiar with what it would take to enable these under machine code take a moment to explain this? I'd also like to know what the associated issues might be. I want to get this sorted out, and am not sure whether it's something I can do myself, or if I need to coax/hire someone to do it for me :) Bill

1 0

7.6.104 beta
by Peter Bortas ＠ Pike developers forum 28 Mar '07

28 Mar '07

http://pike.ida.liu.se/pub/pike/beta/7.6.104/Pike-v7.6.104.tar.gz Me, Grubba, Marcus and Nilsson spent the entire afternoon debugging win32 until we got it working. So this is what I hope is the final release candidate. Ther are more changes than I would have liked since 7.6.102, but they are for real problems in SSL so I can't back them out. Shortlog for changes since: 7.6.102: * All the recent fun time zone stuff. * A bunch of SSL fixes. * Double-free fixed in Shuffle. * Things work on win32 again. Might release it as stable on sunday night unless I come up with a reason not to.

5 10

problems resolving program in a cmod
by Arne Goedeke ＠ Pike developers forum 20 Mar '07

20 Mar '07

I used to do this to get a program of an external class in c: ... push_text("Someclass"); SAFE_APPLY_MASTER("resolv", 1); if (((struct svalue *)(Pike_sp - 1))->type != PIKE_T_PROGRAM) { Pike_error("Could not resolv program Someclass.\n"); } prog = ((struct svalue *)(Pike_sp - 1))->u.program; ... However this does not work for me anymore when I try to resolv a Class that is defined inside the pmod that corresponds to the cmod (in my case in Public.Parser.JSON2 where Public.Parser.___JSON2 is the cmod). Any ideas how to do that? arne

5 13

Parser.XML.Tree
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 19 Mar '07

19 Mar '07

Pretty high latency, I know, but this didn't became a problem until now (again): About a year ago I rewrote the Parser.XML.Tree to be much more object oriented. The major design goal was to be able to easily redefine the produced nodes in the tree. Basically you could do class Node { inherit Parser.XML.Tree.Node; void my_method() { return 7; } } Node n = Node(Stdio.read_file("file.xml")); and get my_method() in all the produced nodes. Today we are however back to the one-class-per-node-type-approach where you basically has to inherit the entire Parser.XML.Tree module to be able to modify its behaviour. Why is that?

3 2

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 March 2007