Pike-devel January 2005

pike-devel@lists.lysator.liu.se

8 participants
29 discussions

amazing adventures with the [*] automap operator
by Martin Bähr 19 Jan '05

19 Jan '05

hi, from time to time i have been wondering if it would not be nice i i could do: foo[3,7,4,2]; and have that return an array ({ foo[3], foo[7], foo[4], foo[2] }) today i thought about this problem once more and i just had the revelation that i could do: foo[ ({ 3,7,4,2 })[*] ]; to produce the desired result. to some of you this may be an old hat, but to me it was a pleasant surprize. pike never ceases to amaze me! thanks guys! greetings, martin.

3 3

array's and %{ ... %}
by Kaos 17 Jan '05

17 Jan '05

I find this as buggy.. or I've missunderstood something: kaos@jenna daemon $ pike -e 'array a = ({ ({ "foo", "bar" }) }); write( "1: %O\n2: %{%O\n%}\n3:%{%O\n%}\n", a, a, a[0] );' 1: ({ /* 1 element */ ({ /* 2 elements */ "foo", "bar" }) }) 2: "foo" 3:"foo" "bar" That is: why only "foo" in case 2 above? I expected to see ({ /* 2 elements */ .... }) //K

3 3

search() bug?
by Martin Bähr 16 Jan '05

16 Jan '05

hi, when doing search i get the following strange error. can anyone explain what this is about? > search(({ 3,4,5,1,2,3 }), "a"); Compiler Error: 1:Bad argument 2 to search. Compiler Error: 1:Expected: function(string, string | int, void | int : int) | function(array((0=mixed)), 0, void | int : int) | function(mapping((1=mixed):(2=mixed)), 2, void | 1 : 1) | !(function(!array, mixed, void | int : mixed) | function(!mapping, mixed, void | int : mixed)) & function(mapping | array, mixed, void | int : zero) Compiler Error: 1:Got : function(array(int(3..3) | int(2..2) | int(1..1) | int(3..5)), string : void | mixed) greetings, martin.

8 11

typeof?
by Martin Bähr 16 Jan '05

16 Jan '05

hi, when looking at this typeof comparison thing, i found the following oddity: > array(string) astr; > array(int) aint; > typeof(astr) < typeof(aint); Result: 1 > typeof(astr) > typeof(aint); Result: 1 how can they both be true? greetings, martin.

3 2

Pike & MinGW
by Bill Welliver 16 Jan '05

16 Jan '05

I thought I'd try my hand at compiling a MinGW pike. I installed nilsson's MinGW package as well as Pike 7.6.24 and had my paths alll set up properly. I had to run bison manually, as the MinGW package i'm using didn't have it, so I modified the makefile to skip over that bit. I also had problems configuring in SQLite, as there are missing source files apparently. The big show stopper right now is sprintf.c: In file included from C:/Program Files/MinGW/Pike/7.7/src/opcodes.h:192, from C:/Program Files/MinGW/Pike/7.7/src/modules/sprintf/sprintf.c:296: C:/Program Files/MinGW/Pike/7.7/src/global.h:84: error: syntax error before "struct" C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:171: error: 'FILE' redeclared as different kind of symbol C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:161: error: previous declaration of 'FILE' was here C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: error: syntax error before "_iob" C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: warning: type defaults to `int' in declaration of `_iob' C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: error: conflicting types for '_iob' C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: error: previous declaration of '_iob' was here C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: error: conflicting types for '_iob' C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: error: previous declaration of '_iob' was here C:/Program Files/MinGW/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdio.h:176: warning: data definition has no type or storage class and so on for several thousand lines. Has anyone seen this problem? Bill

2 1

predef::`== broken?
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 16 Jan '05

16 Jan '05

Pike v7.7 release 13 running Hilfe v3.5 (Incremental Pike Frontend) > ADT.Relation.Binary(); (1) Result: ADT.Relation.Binary(0 0) > object x=_; Compiler Error: 1:Error comparing constants. Compiler Exception: C stack overflow. ... Binary.pike: int(0..1) `==(mixed rel) { if (predef::`==(rel, this)) return 1; // This is never reached.

8 20

pike trace
by Kaos 16 Jan '05

16 Jan '05

Just noticed the very nice feature of trace :) A couple of questions though: a) module.pmod as file name is not very helpfull. Would it be possible to back-up one step in the directory tree when the node is module.pmod to get a sensible filename in the log? b) Is there any tools around for parsing the trace output into some more readable format/graphs? //K

3 3

Re: predef::`== broken?
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 14 Jan '05

14 Jan '05

>>That check has already been performed when lfun::`==() gets called. >> >Does this mean, if lfun::`==() gets called the compared objects are >actually NOT the same object? Otherwise the call would have been avoided? Correct. >--- Ludger Merkens

1 0

segfault with ADT.CircularList
by Martin Bähr 13 Jan '05

13 Jan '05

Pike v7.6 release 7 running Hilfe v3.5 (Incremental Pike Frontend) > ADT.CircularList circular=ADT.CircularList( ({ 1,2,3,4,5 }) ); > (array)circular; (1) Result: ({ /* 5 elements */ 1, 2, 3, 4, 5 }) > circular->push_front(circular->pop_back()); (2) Result: 0 > (array)circular; Segmentation fault whooops! other operations do seem to work. greetings, martin.

1 0

Remote.Obj
by Kaos 13 Jan '05

13 Jan '05

There's a `exists' function in Remote.Obj that is unaccessible without a minor patch. Index: lib/modules/Remote.pmod/module.pmod =================================================================== RCS file: /cvs/Pike/7.6/lib/modules/Remote.pmod/module.pmod,v retrieving revision 1.5 diff -r1.5 module.pmod 973c973 < return get_function(f); --- > return ::`[](f) || get_function(f); 979c979 < return get_function(f); --- > return ::`->(f) || get_function(f); //K

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 January 2005