Pike-devel

pike-devel@lists.lysator.liu.se

3044 discussions

Pike Wiki
by Bill Welliver 09 Sep '05

09 Sep '05

There have been on and off calls for a wiki-like application for people to share information about Pike development and related topics. Not much ever came of it, so I decided to do something about it. I wrote a simple wiki application yesterday and have made it available for anyone to contribute to. Anonymous editing is restricted, in order to minimize possibilities of spam, but the authentication is shared with the pike module repository, so if you've already got a modules.gotpike.org account, you're set to edit. I've started things off with some of my own personal information. Take a moment and share your notes and thoughts (there's a page with notes and guidelines for contributions, please have a look before you post): http://www.gotpike.org/PikeWiki As always, comments and suggestions are welcome. I'll give you all a week or so to bang on it before I share this with the general lists. Bill

2 2

Re: FreeBSD, threads and autoconf.
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 07 Sep '05

07 Sep '05

> Now IDA can do whatever they like... but if they do not, this is one > more time a proof that pike is a language that is dying... IDA provides free hosting. It does not provide free development; that is ambition based, and your words of encouragement are better aimed at the heroes who spend time making Pike better, of their own free will.

1 0

FreeBSD, threads and autoconf.
by Xavier Beaudouin 06 Sep '05

06 Sep '05

Hi there. After thinking *why* coredump generated was getting both libraries libpthreads and libc_r... I have tested pikefarm with forcing library...using --with-thread-library flag. Now it is working right on freebsd.home.oav.net so we can easyly guess the autoconf is b0rken with freebsd > 5.0 about thread support. Since CVS access is not working, can someone patch autoconf to *avoid* -lc_r and -lpthread and/or -lthr on FreeBSD. Defaut that should be used : - FreeBSD < 5.0 : -lc_r (this is the _only_ thread library that exist) - FreeBSD >= 5.0 < 5.3 : -lc_r (but -lkse, -lthr and -lpthread exists. note that -lpthread is -lc_r on these version) - FreeBSD >= 5.4 : -lpthread (but -lc_r, -lthr still exists). Now this will fix all freebsd pikefarm from stock... and help all FreeBSD developpers to *really* find the problems. And this case was not "fix your OS" case, but fix the bloooooody autoconf brain damage. /Xavier

3 2

CVS Write access broken ?
by Xavier Beaudouin 06 Sep '05

06 Sep '05

Hello, I am trying to fix an oddyty with autoconf on freebsd that is still including both -lpthreads and -lc_r on pikefarm... But is seems that CVS is broken ? Can someone check (hostname is kiwi.oav.net). blackmagic:~/cvs/pike/Pike/7.7 kiwi$ cvs update -Pd pike.ida.liu.se: Operation timed out cvs [update aborted]: end of file from server (consult above messages if any) blackmagic:~/cvs/pike/Pike/7.7 kiwi$ cvs update -Pd pike.ida.liu.se: Operation timed out cvs [update aborted]: end of file from server (consult above messages if any) blackmagic:~/cvs/pike/Pike/7.7 kiwi$ /Xavier

2 1

Shootout
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 22 Aug '05

22 Aug '05

The Computer Langauge Shootout has been revived again, and with lots of rewrites they are missing pike tests and asked for our input. http://shootout.alioth.debian.org/sandbox/benchmark.php?test=all&lang=pike&…

2 1

bug tracker
by Martin Bähr 15 Aug '05

15 Aug '05

hi, i am wondering about the state of bug tracking. www.gotpike.org points to alexanders bug tracker which doesn't really seem to get used, while the old tracker at community.roxen.com still sees some use. when alexander set up the tracker, the initiative was welcomed, which seems to indicate that some were not all to happy with crunch. but is hasn't cought on yet. does anyone care which tracker is used? should we point people to both or what would you like to happen in the future? for now i have added a pointer to crunch in the developers section. (something which i started in march, no idea what got me sidetracked, i guess i need a taskmanager for myself) greetings, martin.

3 2

@ for mappings?
by Martin Bähr 15 Aug '05

15 Aug '05

hi, just had a thought for a nice feature that i don't remember having come up here before: for a function with lots of optional arguments it would be nice to take a mapping and splice it up into the args: void foo(void|string s, void|int i, void|float f) could be called as: foo( @([ "f":5.3 ]) ) usefull? greetings, martin.

4 3

embedding
by Bill Welliver 15 Aug '05

15 Aug '05

I was wondering what the status was of embedding that was being worked on by a few people. I was wondering if it would be possible to get a status, and maybe a look at the code (even if it's non-working) Bill

4 9

7.7 changes
by Jonas Walld�n ＠ Pike developers forum 14 Aug '05

14 Aug '05

I question the correctness of the changes checked into 7.7 last night by Nilsson (CVS comment "No longer allocate unused space for terminating char."). The +1 was not intended for accomodating a terminating character but to make sure zero-sized images get handled correctly in case malloc(0) returns NULL.

2 6

Valgrind
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 14 Aug '05

14 Aug '05

Valgrind complains about uninitialized values in the decoder in Pike 7.7. ==4485== Conditional jump or move depends on uninitialised value(s) ==4485== at 0x8116695: override_identifier (/home/nilsson/Pike/7.7/src/program.c:1912) ==4485== by 0x80B809B: decode_value2 (/home/nilsson/Pike/7.7/src/encode.c:3976) ==4485== by 0x80B9549: low_do_decode (/home/nilsson/Pike/7.7/src/encode.c:4324) ==4485== by 0x80B9791: my_decode (/home/nilsson/Pike/7.7/src/encode.c:4457) ==4485== by 0x80B9E31: f_decode_value (/home/nilsson/Pike/7.7/src/encode.c:4776) ==4485== by 0x807AF3A: opcode_F_CALL_BUILTIN (/home/nilsson/Pike/7.7/src/interpret_functions.h:2231) ==4485== by 0x1C07A236: ??? ==4485== by 0x807ECE5: o_catch (/home/nilsson/Pike/7.7/src/interpret.c:2100) ==4485== by 0x8075E5B: jump_opcode_F_CATCH (/home/nilsson/Pike/7.7/src/interpret_functions.h:1290) ==4485== by 0x1C079F86: ??? ==4485== by 0x807EBF0: mega_apply (/home/nilsson/Pike/7.7/src/interpret.c:2055) ==4485== by 0x807FF61: apply (/home/nilsson/Pike/7.7/src/interpret.c:2448) ==4485== Conditional jump or move depends on uninitialised value(s) ==4485== at 0x80B7317: decode_value2 (/home/nilsson/Pike/7.7/src/encode.c:4151) ==4485== by 0x80B9567: low_do_decode (/home/nilsson/Pike/7.7/src/encode.c:4327) ==4485== by 0x80B9791: my_decode (/home/nilsson/Pike/7.7/src/encode.c:4457) ==4485== by 0x80B9E31: f_decode_value (/home/nilsson/Pike/7.7/src/encode.c:4776) ==4485== by 0x807AF3A: opcode_F_CALL_BUILTIN (/home/nilsson/Pike/7.7/src/interpret_functions.h:2231) ==4485== by 0x1C07A236: ??? ==4485== by 0x807ECE5: o_catch (/home/nilsson/Pike/7.7/src/interpret.c:2100) ==4485== by 0x8075E5B: jump_opcode_F_CATCH (/home/nilsson/Pike/7.7/src/interpret_functions.h:1290) ==4485== by 0x1C079F86: ??? ==4485== by 0x807EBF0: mega_apply (/home/nilsson/Pike/7.7/src/interpret.c:2055) ==4485== by 0x807FF61: apply (/home/nilsson/Pike/7.7/src/interpret.c:2448) ==4485== by 0x80B3061: decode_value2 (/home/nilsson/Pike/7.7/src/encode.c:2712)

2 1

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