Pike-devel September 2004

pike-devel@lists.lysator.liu.se

8 participants
36 discussions

Pike 7.6.13 for win32 bhelliom-beta1
by Peter Bortas ＠ Pike developers forum 17 Sep '04

17 Sep '04

There is a new 7.6 win32 beta on ftp, but since I forsee problems accessing it I've also uploaded it to http://www.lysator.liu.se/~zino/Pike-7.6.13-win32-bhelliom-beta1.exe It is tested to the extent that I have started Hilfe and written "indices(SDL);" which worked well enough. It should also included all needed DLLs. Known misfeature: The pike binary doesn't have an icon.

6 12

pike terminology: method or function?
by Martin Bähr 17 Sep '04

17 Sep '04

hi, when reading through our documentation i observed an inconsistency in our terminology: which is the preffered term? the module tree reference and the reference manual seem to use function, however the beginners tutorial uses method, and claims in http://pike.ida.liu.se/docs/tutorial/methods/ Most programming languages allow you to divide your program into smaller parts. These can be called ßub-routines", "procedures", "functions" or "methods". In Pike, we use the term "method". i believe this is simply not true, as far as i remember we have always used the term function, and the name of the respective keyword strongly suggests that we should stick with that. comments?

3 2

Caudium 1.4.2 (RC1) is out !
by Xavier Beaudouin 15 Sep '04

15 Sep '04

The Caudium Group is pleased to announce that Caudium 1.4.2 (RC1) webserver is out. After more than 1.5 years of development, Caudium 1.4 branch is running natively on Pike 7.6. Numerous changes has been done and lot of code has been changed. Mostly some Pike code changed into C for speed purposes. You can download it at : http://caudium.net/download/source/download.rxml? version=1.4.2&bzsize=5.4&gzsize=6.1&change=yes Change log is at : ftp://ftp.caudium.net/caudium/source/caudium-1.4.2.CHANGES Enjoy, test, and send us bugs reports ! /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

1 0

Failure to compile Pike 7.6 on FreeBSD sparc 64 :
by Xavier Beaudouin 14 Sep '04

14 Sep '04

Hello there, There is a problem compiling on FreeBSD Sparc 64 (FreeBSD 5.3-BETA4) : gmake[3]: Leaving directory `/usr/ports/lang/pike76/work/pike-7.6.13/src/modules/Image/encodings' Compiling search.c {standard input}: Assembler messages: {standard input}:10476: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10498: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10500: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10514: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10516: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10538: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10540: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10554: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10556: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10804: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10806: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10828: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10830: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10844: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10846: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10868: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10870: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10884: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10886: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11159: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11181: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11183: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11197: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11199: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11221: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11223: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11237: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11239: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11484: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11506: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11508: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11522: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11524: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11546: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11548: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11562: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:11564: Error: Illegal operands: There are only 32 single precision f registers; [0-31] WARNING: Compiler failure! Trying without optimization! {standard input}: Assembler messages: {standard input}:9741: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9763: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9765: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9779: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9781: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9803: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9805: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9819: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:9821: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10063: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10065: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10087: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10089: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10103: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10105: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10127: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10129: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10143: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10145: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10410: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10432: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10434: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10448: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10450: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10472: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10474: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10488: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10490: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10729: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10751: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10753: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10767: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10769: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10791: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10793: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10807: Error: Illegal operands: There are only 32 single precision f registers; [0-31] {standard input}:10809: Error: Illegal operands: There are only 32 single precision f registers; [0-31] Compilation command was: /usr/ports/lang/pike76/work/pike-7.6.13/src/smartlink cc -I. -I/usr/ports/lang/pike76/work/pike-7.6.13/src/modules/Image -I/usr/ports/lang/pike76/work/pike-7.6.13/src -I/usr/ports/lang/pike76/work/pike-7.6.13/src -I/usr/ports/lang/pike76/work/pike-7.6.13/src/bundles/include -I/usr/local/include -DHAVE_CONFIG_H -O -pipe -ffast-math -fomit-frame-pointer -I/usr/ports/lang/pike76/work/pike-7.6.13/src/bundles/include -I/usr/local/include -c search.c -o search.o gmake[2]: *** [search.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/pike76/work/pike-7.6.13/src/modules/Image' gmake[1]: *** [Image] Error 1 gmake[1]: Leaving directory `/usr/ports/lang/pike76/work/pike-7.6.13/src/modules' gmake: *** [module_objects] Error 1 *** Error code 2 bash-2.05b# gcc -v Using built-in specs. Configured with: FreeBSD/sparc64 system compiler Thread model: posix gcc version 3.4.2 [FreeBSD] 20040728 bash-2.05b# uname -a FreeBSD ws01.home.oav.net 5.3-BETA4 FreeBSD 5.3-BETA4 #0: Sun Sep 12 09:11:49 UTC 2004 root@bobbi.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC sparc64 How this can be fixed ???? /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

5 8

Stdio.FILE delimiter
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 14 Sep '04

14 Sep '04

The FILE object always uses \n as line delimiter, which is good for consistent behaviour across platforms (if your parse the same file with the same code on two machines you get the same result), but bad for consistent behaviour across platforms (if you run a code that reads stdin you may get different results on different machines). So. Newline delimiters needs to be configurable, but how should this feature work, and what is its default?

2 1

List
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 12 Sep '04

12 Sep '04

grubba, could you give a description of the new List type and how it relates to the stuff in the ADT-module?

2 1

gethostip
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 11 Sep '04

11 Sep '04

Parsing ifconfig output is boring, so something like this could perhaps be added? I'm not adding it myself, since network/socket/ioctl-stuff isn't my best area. static void f_gethostip(INT32 args) { int fd, i, j, up; struct ifconf ifc; struct sockaddr_in addr; char buffer[ INTERFACES * sizeof( struct ifreq ) ]; pop_n_elems(args); fd = fd_socket( AF_INET, SOCK_DGRAM, IPPROTO_UDP ); if( fd < 0 ) Pike_error("gethostip: Failed to open socket.\n"); ifc.ifc_len = sizeof( buffer ); ifc.ifc_ifcu.ifcu_buf = (caddr_t)buffer; if( ioctl( fd, SIOCGIFCONF, &ifc ) < 0 ) Pike_error("gethostip: Query failed.\n"); up = 0; for( i=0; i<ifc.ifc_len; ) { struct ifreq *ifr = (struct ifreq *)( (caddr_t)ifc.ifc_req+i ); struct ifreq ifr2; i += sizeof(struct ifreq); strcpy( ifr2.ifr_name, ifr->ifr_name ); if( ioctl( fd, SIOCGIFFLAGS, &ifr2 )<0 ) Pike_error("gethostip: Query failed.\n"); if( (ifr2.ifr_flags & IFF_LOOPBACK) || !(ifr2.ifr_flags & IFF_UP) || (ifr->ifr_addr.sa_family != AF_INET ) ) continue; push_text( ifr->ifr_name ); memcpy( &addr, &ifr->ifr_addr, sizeof(ifr->ifr_addr) ); push_text( inet_ntoa( addr.sin_addr ) ); up++; } fd_close(fd); f_aggregate_mapping(up*2); }

5 12

packages for pike on solaris?
by Martin Bähr 11 Sep '04

11 Sep '04

hi, i believe we do have a number of solaris friends here, wouldn't it be nice to have pike packages for the Community Open Source Software Distribution for The Solaris Operating Environment at http://www.blastwave.org/ ? greetings, martin.

1 0

win32 gmp
by Peter Bortas ＠ Pike developers forum 10 Sep '04

10 Sep '04

What version of Gmp was last known to work as a bundle on win32? (Mostly directed at Grubba, but if anyone else knows, feel free to answer.)

1 0

Pike Conference Registration is now open!
by Bill Welliver 10 Sep '04

10 Sep '04

Pike Conference 2004 Essen, Germany October 13 - 19, 2004 Pike - Caudium - Roxen - sTeam - LPC - psyc/muve It's only one more month until the Pike Conference begins, and the registration is now open. Current topics for the conference include: Pike: The year in review and a look ahead Developer's Tools: Current and Future Marketing: How to promote Pike Pike for Beginners: a Tutorial Introductory CMOD Development Creating Modules for the Pike Module Repository This year's keynote will be presented by Uwe A�mann from the University of Dresden. We welcome proposals for talks, workshops and presentations by Pike users and developers. Please submit your proposal by October 1st. Please contact the conference committee at conference(a)gotpike.org for more details. In addition to talks, workshops and tutorials at the Pike Conference, the Caudium conference is being held at the same time, so you'll be able to participate in Caudium-specific sessions as well. This year's conference is being held at the Unperfekthaus in Essen. The entire house is wired for networking, and wireless LAN is also reachable in most places. We have arranged a quiet work area for those that need to spend time working for their employers. If you have financial troubles, talk to us and let us see if we can work something out. If you're not able to join us for the entire conference, you're welcome to stay as long as you can. We'd rather have you for a few days rather than not at all. For more information, and to register, please visit the Pike Conference 2004 website: http://conference.gotpike.org We look forward to seeing you in Essen! Bill Welliver and Martin B�hr Conference Co-chairs conference(a)gotpike.org

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 September 2004