Pike-devel

pike-devel@lists.lysator.liu.se

3 participants
3048 discussions

Re: links for bleeding edge source packages
by Peter Bortas ＠ Pike developers forum 20 Sep '04

20 Sep '04

That looks like dists and smells like dists, but it sure ain't dists. Please at least fix the URL to contain the appropriate warnings. / Peter Bortas Previous text: >2004-09-20 20:05: >Subject: Re: links for bleeding edge source packages >-------------------------------------------------------------------- >ftp://ftp.caudium.net/pike/7.7/ > >/xavier >Le 20 sept. 04, à 15:45, Michael J. Stenitzer @ Pike developers forum a >écrit : > >> wouldn't it be nice to have links for the latest source packages >> exportet by pikefarm at the website. >> >> i can only find >> http://pike.ida.liu.se/generated/pikefarm/packages/7.7/latest at the >> download page and currently i always change the url manually to >> download >> the latest code for 7.4, 7.6 etc. (or did i miss a different download >> place?) >> >> /m >> >-- >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 > > > > / Brevbäraren >

1 0

links for bleeding edge source packages
by Michael J. Stenitzer ＠ Pike developers forum 20 Sep '04

20 Sep '04

wouldn't it be nice to have links for the latest source packages exportet by pikefarm at the website. i can only find http://pike.ida.liu.se/generated/pikefarm/packages/7.7/latest at the download page and currently i always change the url manually to download the latest code for 7.4, 7.6 etc. (or did i miss a different download place?) /m

1 0

Bug in FileStat
by David Gourdelier 20 Sep '04

20 Sep '04

With Pike 7.6 CVS: object file = Stdio.File("/tmp/toto"); file->stat()->size; (2) Result: 17592186044416 > file->stat()->size; (3) Result: 17592186044416 > object file = Stdio.File("/tmp/mysqldump.sql"); > file->stat()->size; (4) Result: 17592186044416 With Pike 7.6.13 "official": > object file = Stdio.File("/tmp/toto"); > file->stat(); (1) Result: Stat(drwxr-xr-x 1024b) > file->stat()->size; (2) Result: 1024 > object file = Stdio.File("/tmp/mysqldump.sql"); > file->stat()->size; (3) Result: 980004 OS is Linux. / David

8 16

values for character literals?
by Martin Bähr 19 Sep '04

19 Sep '04

hi, does the translation of character litarals such as: 'b' or 'ö' depend on the character set i am using or will it always be the unicode value? how is the characterset determined? greetings, martin.

3 2

values for character literals?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 19 Sep '04

19 Sep '04

I think you can also use UTF-16 without explicitly declaring it, if the file starts with a BOM.

1 0

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

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