Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

subversion bindings
by Martin Baehr 12 Nov '02

12 Nov '02

hi, at the pike conference there was mention of pike bindings for subversion. what is the status of that? greetings, martin.

2 9

pike.el
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 12 Nov '02

12 Nov '02

I've written most of the font locking code in tools/pike.el. Now I'd like to move the parts that handles autodoc comments to CC Mode. Would there be any license problems doing that? The code will then fall under the copyright assignment agreement I have with the FSF.

8 30

More about ADTs
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 12 Nov '02

12 Nov '02

> > Yes it should be _equal() > > Excellent solution, actually. Didn't think of that. That is, it probably still shouldn't throw errors, since equal() can be used on arbitrary structures too, and there might be cases when the caller doesn't know what things it might encounter during its recursion. But it's still an excellent idea to use _equal instead of `==, so that == can be used to check whether the arguments are the same iterator.

1 0

binary number representation
by Martin Nilsson (Fake Build Master) ＠ Pike (-) developers forum 11 Nov '02

11 Nov '02

The documentation http://pike.ida.liu.se/generated/manual/ref/chapter_3.html says that a binary int may be written as -?0[bB][01]+

1 0

binary number representation
by Peter Lundqvist (disjunkt) ＠ Pike (-) developers forum 11 Nov '02

11 Nov '02

I'm not entierly convinced about the need for this, but perhaps it could be usefull (I recently had to poke at some x86 assembler with tasm, that's why I ask). Would it be possible to add binary number representation to pike? That is [0-9]* - dec 0[0-7]* - oct 0x[0-9A-Fa-f]* - hex [01]*b - binary I don't really need it (it's easy enough to convert binary to hex in head) but perhaps it does have som use for the base convertingly challanged?

3 2

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

Jump to page:

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