Pike-devel January 2003

pike-devel@lists.lysator.liu.se

11 participants
88 discussions

INT_TYPE = INT64
by Mirar ＠ Pike developers forum 26 Jan '03

26 Jan '03

And now I found that bug too. Pike was absolutely correct, the variable rxml_mode in this struct: | struct xmlobj | { | struct mapping *entities; | struct mapping *attributes; | struct mapping *is_cdata; | int rxml_mode; | }; was clearly outside the object struct as an INT_TYPE. I wonder how many such bugs there is in Pike...

1 0

INT_TYPE = INT64
by Mirar ＠ Pike developers forum 26 Jan '03

26 Jan '03

Now I got the Gmp.mpz glue working too. Seems like the detection of large integers were broken, but the needed supporting code were still intact. I can't spot anything that doesn't work now, except the testsuite.

1 0

INT_TYPE = INT64 (Bz2)
by Mirar ＠ Pike developers forum 26 Jan '03

26 Jan '03

I added a semi-kludge now, that puts the min and max values in range, to MIN_ and MAX_INT32 respectively if the value was outside the range. (Only active if SIZEOF_INT_TYPE>4.)

1 2

7.5/7.6 roadmap?
by Alexander Demenshin 24 Jan '03

24 Jan '03

Hi, Is there any roadmap or at least goals - what will (planned to) be implemented in Pike 7.5/7.6? What will be advantages comparing to 7.4? Regards, /Al

1 0

Two questions
by Peta, jo det �r jag ＠ Pike developers forum 24 Jan '03

24 Jan '03

sorry i guess it should be PIKEFUN void create(object l)

1 0

Gmp testsuite
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 23 Jan '03

23 Jan '03

| Making verify in build/sunos-5.9-sun4m | ( cd modules && make testsuites ) | | /usr/ccs/bin/m4:-:/home/xenofarm/xenoclient/pike-7.4/buildtmp/Pike7.4-20030122-151319/src/modules/Gmp/testsuite.in:208 | pushed back more than 4096 chars | DOTEST(TRUE,mixed a() { return Gmp.mpz(1.0)<Gmp.mpz(2.0); }) Maybe it's time to do something about the explosive nature of the macro expansions in the Gmp testsuite? I'm pretty sure they generate far more tests than are actually useful anyway.

2 2

Stdio.port listen() backlog again...
by Alexander Demenshin 22 Jan '03

22 Jan '03

Hi everyone, I posted this once on Pike list, and got no reply, so I am trying here, perhaps devel list is better place... > I found that it is impossible to specify backlog parameter when > using Stdio.Port - it is hardcoded to 16384. > > Actually, the questions are - what should I do to actually limit > backlog value? And - why it is hardcoded? Problem with current implementation: it is relatively easy to make a DoS attack against everything that listening through Stdio.Port (most used apps: Roxen & Caudium). Any comments? :) Regards, /Al

9 19

Parent reference semantics.
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 22 Jan '03

22 Jan '03

Poll: Given the following files: A.pmod: void foo() { werror("A\n"); } class B { void bar() { foo(); } } C.pike: inherit .A.B; void baz() { foo(); } void foo() { werror("C\n"); } Should the following program: int main() { object c = .C(); c->bar(); c->baz(); } Output A C or C C ? ie Should parent references be overloadable via inherit?

6 8

Parent reference semantics.
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 22 Jan '03

22 Jan '03

In order to overload bar(), you need to inherit A.

1 0

Whee!
by David Hedbor ＠ Pike developers forum 17 Jan '03

17 Jan '03

First successful icc build of Pike 7.5 just finished. :)

2 3

← Newer
1
2
3
4
5
6
7
8
9
Older →

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 2003