Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Start a nNew thread

combine_path()
by Peter Bortas ＠ Pike developers forum 11 Nov '02

11 Nov '02

Is this clipping of the path intentional? > combine_path("/foo","/bar","gaz"); Result 3: "/bar/gaz"

2 1

'Outsider finds a bug and fix'
by dnewmon ＠ Pike developers forum 10 Nov '02

10 Nov '02

I found a bug in Math.Angle Watch this bug in action: Angle ang = Angle(); ang->set("deg",90); write(ang->get("rad") + "\n"); ang->set("deg",90); write(ang->get("rad") + "\n"); The problem: Angle set_rad(int|float rad) { angle = rad; normalize(); type = "rad"; // this should be before the normalize() call return this_object(); } The solution: Angle set_rad(int|float rad) { angle = rad; type = "rad"; normalize(); return this_object(); } Do the same with set_gon and set_degree also. Another note: The following line causes normalize() to be called before 'type' is set to anything. So the switch(type) statement in normalize() doesn't do anything to make sure the angle is within range. Angle ang = Angle(); C-Ya, David Newmon (dnewmon(a)yahoo.com)

2 1

psparser.c
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 10 Nov '02

10 Nov '02

[...] switch(cptr[3]) { case 0xC0 ... 0xDF: [...] I'm sorry to say, but this is not C. §6.6.4.2:1 of C99 (the current C standard says): | The controlling expression of a switch statement shall have integer | type, and shall not cause a block to be entered by a jump from outside | the block to a statement that follows a case or default label in the | block (or an enclosed block) if that block contains the declaration of | a variably modified object or variably modified typedef name. The ^^^ | expression of each case label shall be an integer constant ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | expression. No two of the case constant expressions in the same switch ^^^^^^^^^^ | statement shall have the same value after conversion. There may be at | most one default label in a switch statement. (Any enclosed switch | statement may have a default label or case constant expressions with | values that duplicate case constant expressions in the enclosing | switch statement.) "0xC0 ... 0xDF" is not an integer constant expression, so this is not legal C.

3 6

0.6 support in nt-tools
by Peter Bortas ＠ Pike developers forum 07 Nov '02

07 Nov '02

Does anyone have need of the Pike 0.6 support in nt-tools, or can I clear that out while I fix other things?

2 1

Unicode/normalize.c:67: '_c' undeclared here
by Honza (hop) Petrous ＠ Pike (-) developers forum 07 Nov '02

07 Nov '02

It's a very strange, but 7.3 compilation is complaining about undeclared symbols: [..] make[3]: Entering directory `/root/7.3-cvs-021105/build/bezgtk/post_modules/Unicode' Compiling /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:67: `_c' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:67: `_c' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:70: `_d' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:70: `_d' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:73: `_ca' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:73: `_ca' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c: In function `init_hashes': /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:90: `_d' undeclared (first use in this function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:90: (Each undeclared identifier is reported only once /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:90: for each function it appears in.) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:97: `_c' undeclared (first use in this function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:104: `_ca' undeclared (first use in this function) WARNING: Compiler failure! Trying without optimization! cc1: warning: -Wuninitialized is not supported without -O /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:67: `_c' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:67: `_c' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:70: `_d' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:70: `_d' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:73: `_ca' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:73: `_ca' undeclared here (not in a function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c: In function `init_hashes': /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:90: `_d' undeclared (first use in this function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:90: (Each undeclared identifier is reported only once /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:90: for each function it appears in.) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:97: `_c' undeclared (first use in this function) /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c:104: `_ca' undeclared (first use in this function) Compilation command was: /root/7.3-cvs-021105/build/bezgtk/smartlink gcc -I. -I/root/7.3-cvs-021105/src/post_modules/Unicode -I/root/7.3-cvs-021105/build/bezgtk -I/root/7.3-cvs-021105/src -I/usr/X11R6/include -g -mcpu=i686 -I/usr/X11R6/include -W -Wall -Wno-unused -Wcomment -Wformat -Wimplicit-function-declaration -Wmultichar -Wswitch -Wuninitialized -Wpointer-arith -Wchar-subscripts -Wno-long-long -c /root/7.3-cvs-021105/src/post_modules/Unicode/normalize.c -o normalize.o make[3]: *** [normalize.o] Error 1 make[3]: Leaving directory `/root/7.3-cvs-021105/build/bezgtk/post_modules/Unicode' make[2]: *** [Unicode] Error 1 make[2]: Leaving directory `/root/7.3-cvs-021105/build/bezgtk/post_modules' make[1]: *** [post_module_objects] Error 1 make[1]: Leaving directory `/root/7.3-cvs-021105/build/bezgtk' make: *** [all] Error 2 [root@elrond bezgtk]#

2 4

More about ADTs
by Peta, jo det �r jag ＠ Pike developers forum 07 Nov '02

07 Nov '02

A few comments... The add() method is still there, I believe that a method to insert without giving an index is useful in a sequence. The insert and delete methods are not named _insert and _delete, this has three reasons. 1) There is currently no lfun insert and delete. 2) I belive that it should be possible to remove and insert without using and lfun 3) If there will be a insert and delete lfun then it should not be difficult to use the current insert and delete methods. A few words about the coming ADTs It will probably be an ordered map maybe a sequence, a set, a priority list and a heap, based on a binary tree and a sequence, a queue and a stack based on a double linked list and finally wrappers for mapping, multiset and array.

1 0

RIS CVS for 7.3
by Marek Habersack (Grendel) ＠ Pike (-) developers forum 04 Nov '02

04 Nov '02

It seems that the RIS mirror of the IDA Pike 7.3 repository is quite out of date. Does anybody know anything closer about it?

2 1

Optimizations
by Martin Nilsson (Fake Build Master) ＠ Pike (-) developers forum 04 Nov '02

04 Nov '02

I've run some of the shootout tests with disabled optimizations and found some surprising results: Pike: pike PikeNP: pike -dp (without peephole optimization) PikeNT: pike -dt (without tail recursion) PikeNTP: pike -dp -dt Pike PikeNP PikeNT PikeNTP 1: 42.81 32.83 37.49 34.75 (ackermann) 2: 34.92 37.05 37.64 37.80 (ary3) 3: 148.92 304.90 118.21 128.94 (fibo) Is the test flawed or is there something fishy in the optimization. The compilation overhead between Pike with and without optimizations is at most 0.13s.

4 5

lyskom export problems?
by Martin Baehr 04 Nov '02

04 Nov '02

the export mailing list is getting multiple copies of each message with different dates (2-3 minutes different) since today. what's happening? is the exporter trying to compensate for the lack of messages over the last few days? greetings, martin.

2 1

Backend stuff in 7.3
by Marek Habersack (Grendel) ＠ Pike (-) developers forum 03 Nov '02

03 Nov '02

Would it be possible to get a quick overview about how to use it? Looking through backend.cmod doesn't give much information. If I understand that well, Backend_struct is a transparent structure used in a generic way by backend.cmod - if it is so, where can I find specs about what does backend.cmod expect to find in the structure? I'd like to implement my own I/O backend and it seems that Backend_struct somehow makes it possible. How? :) TIA

1 0

Jump to page:

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