Pike-devel April 2007

pike-devel@lists.lysator.liu.se

3 participants
18 discussions

Re: Need another GC policy
by H. William Welliver III 22 Apr '07

22 Apr '07

It's probably worth noting that the Java garbage collector does suffer from many of the same problems, even if there are no "scheduled" runs. The main problem here is that the gc runs in a "stop the world" fashion. I'm not sure if that can be avoided completely. Bill >> I'm not well-known in gc algorithms, but a garbage collector like >> Java does not require scheduled runs, so no stalls there. Why not >> pike?

2 1

GLUE
by Mirar ＠ Pike developers forum 17 Apr '07

17 Apr '07

Now I'm missing GLUE.Font, base/Font.pike:14:Index Font not present in module "GLUE". base/Font.pike:14:Illegal program identifier: 0. base/Font.pike:42:Index Font not present in module "GLUE". base/Font.pike:44:Index Font not present in module "GLUE". base/bumpy.pike:14:Error looking up 'Font' in module '.'. I didn't see GLUE change when I updated, and it's in there in module.pmod. What up?

1 0

7.7 continues
by Mirar ＠ Pike developers forum 17 Apr '07

17 Apr '07

Trying to build a Pike with --with-long-long-int and --with-double-precision: | /home/mirar/pike/build/linux-2.6.17-11-generic-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/mirar/pike/build/linux-2.6.17-11-generic-x86_64/master.pike /home/mirar/pike/src/post_modules/Shuffler/make_sources.pike /home/mirar/pike/src/post_modules/Shuffler sources.h sources_to_compile | -:1: Type mismatch for callback function `!: | -:1: Expected: function( : int(2147483647..2147483647)) | -:1: Got : function( : int(0..1)) | -:1: Program constant "Iterator" is NULL. | make[2]: *** [override] Segmentation fault (core dumped) I can't even begin to spot what's going wrong here. Should I assume Pike 7.7 is so severly broken it's no use trying to get it to work?

3 3

Pike 7.6.108 beta
by Peter Bortas ＠ Pike developers forum 17 Apr '07

17 Apr '07

http://pike.ida.liu.se/pub/pike/beta/7.6.108/Pike-v7.6.108.tar.gz http://pike.ida.liu.se/pub/pike/beta/7.6.108/Pike-v7.6.108.1-win32.exe Changes since last beta: o Fixed mktime to work better with out of bounds time fields. [bug 4326] o Fixed support for big endian 64-bit. o Fixed -t (tracing) on win32. o Fixed GL on win32. (aka AIDO starts and can play media streams.)

4 10

building pike with pike (7.7 cvs)
by Mirar ＠ Pike developers forum 15 Apr '07

15 Apr '07

>bin/mkpeep.pike:463:Too many arguments to sprintf. >bin/mkpeep.pike:463:Expected: function(string(8), int(0..2147483647) : string) >bin/mkpeep.pike:463:Got : function(string(8), int, string : void | mixed) > >463: buf->add_line( sprintf("%*n}", ind, test) ); Er, I see now the problem is that »test» is a string, so it is a bug in mkpeep...

2 3

building pike with pike (7.7 cvs)
by Mirar ＠ Pike developers forum 15 Apr '07

15 Apr '07

I suspect these problems depend on the new typechecker... bin/mkpeep.pike:463:Too many arguments to sprintf. bin/mkpeep.pike:463:Expected: function(string(8), int(0..2147483647) : string) bin/mkpeep.pike:463:Got : function(string(8), int, string : void | mixed) 463: buf->add_line( sprintf("%*n}", ind, test) ); Can't work around that. Copying an old peep.c, bin/precompile.pike:2006:Too many arguments to sprintf. bin/precompile.pike:2006:Expected: function(string(8), object | int, object | string, object | int, object | string : string) bin/precompile.pike:2006:Got : function(string(8), int, string, int, string, string : void | mixed) 2006: PC.Token(sprintf("if(Pike_sp[%d%s].type != PIKE_T_STRING || Pike_sp[%d%s].ustring -> width)", 2007: argnum,check_argbase, 2008: argnum,check_argbase, 2009: upper_case(arg->basetype())),arg->line()) This is true, however I don't think "too many arguments to sprintf" should be an error, but a warning, unless it's strict_types. (But that's my personal opinion.)

1 0

sprintf() arguments now type checked in Pike 7.7.
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 13 Apr '07

13 Apr '07

I've added some type checking support for sprintf() arguments: New type checker: > sprintf("%s%i%f\n", 17, "", 14.0); Compiler Error: 1:Error in format string, i is not a format. Compiler Error: 1:Bad argument 2 to sprintf. Compiler Error: 1:Expected: object | string Compiler Error: 1:Got : int(17..17) Compiler Error: 1:Bad argument 3 to sprintf. Compiler Error: 1:Expected: object | float Compiler Error: 1:Got : string(0) Compiler Error: 1:Too many arguments to sprintf (expected 3 arguments). Compiler Error: 1:Got : float Old type checker: > sprintf("%s%i%f\n", 17, "", 14.0); Compiler Error: 1:Error in format string, i is not a format. Compiler Error: 1:Too many arguments to sprintf. Compiler Error: 1:Expected: function(string(8), object | string, object | float : string) Compiler Error: 1:Got : function(string(8), int(17..17), string(0), float : void | mixed)

2 2

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

02 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

2026

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