Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

SQLite module (7.7) notes
by Alexander Demenshin 03 Nov '04

03 Nov '04

Hi, Just tried this beast (FYI: compiles and works in 7.6 as well), however there are some (minor) issues: - There is no query() method, which is inconvenient for simple statements like INSERT or DELETE - statement won't be executed with big_query() unless fetch_row() in result is called, which, in turn, makes code a bit ugly. - When sleeping (in case of SQLITE_BUSY) - may be it makes sense to enable threads? Even 100 ms is quite a lot. Optionally, it might be useful to allow dynamic configuration of this interval. - Again when sleeping - there is no limit for sleeping, and (in theory) it could happen that we will sleep forever (buggy external lock or so). Regards, /Al

2 3

Install broken?
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 02 Nov '04

02 Nov '04

Are the installation scripts broken in 7.7-cvs right now? Seems to me that Grubbas checkins broke it, but I'm not sure and I don't have time to investigate right now.

2 2

Bug/Issue tracking?
by Alexander Demenshin 02 Nov '04

02 Nov '04

Hi, Is there any kind of BTS for Pike development? If "no", any plans to use one? Regards, /Al

2 1

Re: pike ftp again (was: FreeBSD Port of Roxen 4.0)
by Xavier Beaudouin 02 Nov '04

02 Nov '04

Le 1 nov. 04, à 14:50, Martin Bähr a écrit : > On Mon, Nov 01, 2004 at 02:38:04PM +0100, Xavier Beaudouin wrote: >> When IDA ftp will working... but I cannot make it working on passive, >> not passive or what ever... >> >> ftp.caudium.net/pike/ftp.ida.liu.se is out of sync since more than 2 >> months... so I cannot get an "official" version of pike .... > > this is bad. > lots of people have problems accessing the pike server through ftp. > we need a mirror that works. > > is there any chance to get ftp fixed in linköping? > > xavier: what made your mirror stop working? FTP Passive is NOT working on pike ftp server. This is not a problem about my ftp client firewall or whatever. To get pike I must not have a firewall and use Active FTP... whatever Pike.Ida's ftp server is saying the packet never come to the internet. > is there a way to set up alternatives to access the server? > ssh (for those of us who have writeaccess to the repository already) > rsync server? > rsync or ftp upload to the caudium mirror (the caudium mirror runs an > rsync server i believe) It does for slaves mirrors (eg ftp.us.caudium.net). I have temporaly fixed that by : 02500 29 1392 allow tcp from 130.236.182.30 to me setup in my ipfw configuration, but I *don't* like to have a naked machine on the net trusted a server I don't adminstrate... How to fix that : - make passive FTP working (simple just configure a range of passive ports in IDA's firewall) or - make ftp archive from IDA that can be accessible by rsync... Here is my 0,02c.... /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

3 3

TinyCC support
by Marcus Agehall (PacketFront) ＠ Pike (-) developers forum 01 Nov '04

01 Nov '04

(Perhaps this should be sent to the TinyCC devel list, but I'll start here..) I tried compiling pike using the latest TinyCC. It fails when compiling the image-module due to some preprocessing problems: In file included from /home/marage/src/Pike/7.7/src/modules/Image/image_module.c:23: /home/marage/src/Pike/7.7/src/modules/Image/encodings/encodings.h:36: warning: pasting "img_ilbm" and "##" does not give a valid preprocessing token This seems a bit strange to me. I've looked at the ANSI-standard for CPP and I cannot see how this use of ## is in violation of the standard. Can someone here verify that the Pike-code is valid and that I should go bug the TinyCC developer instead?

2 4

Unicode escapes
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 31 Oct '04

31 Oct '04

I'm thinking of adding an escape mechanism to be able to format wide strings a bit better. Right now there's the choice between sprintf %s which just let wide chars straight through, and %O which quotes them along with all other control chars. Neither is really good if you want to e.g. print a string to stdout which possibly can contain some wide chars. For that I'd like to add a %S that only quotes wide chars in some way. The question is what quoting method to use. Java and many other languages has one with "\u" which always is followed by four hexadecimal digits. (Java doesn't say anything about chars wider than 16 bits, but I guess it's "\U" followed by eight hexadecimal digits, as in some generic Unicode technical papers.) Java also specifies a way to keep it unambiguous: If a string already contains a sequence like "\u4711" it's quoted by inserting another "u", i.e. it becomes "\uu4711". The \u and \U scheme is better than the \4711 and \x9c9 escapes that Pike uses in strings since there's no ambiguity where the escape sequence ends (%O uses tricks like "\4322""33" to cope with them but that doesn't work very well in strings without quotes around them). The ad-hoc quoting scheme "<nnnnn>" used in some places in describe_svalue would also be replaced by this for consistency.

1 0

free_program
by Martin Nilsson (DivX Networks) ＠ Pike (-) developers forum 30 Oct '04

30 Oct '04

Where is the code for really_free_program?

1 1

Re: string[x..<y]
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 30 Oct '04

30 Oct '04

I mean a[<-1..] of course; a[sizeof(a)..] is represented easily.

1 0

Re: string[x..<y]
by Mirar ＠ Pike developers forum 30 Oct '04

30 Oct '04

(This will of course completely destroy the case where you want to use the end-operator with another type then int, but meh...)

1 0

Re: string[x..<y]
by Mirar ＠ Pike developers forum 30 Oct '04

30 Oct '04

Note the difference to this: arr[ ..< 1] == arr[ ..sizeof(arr)-2] arr[ ..< 0] == arr[ ..sizeof(arr)-1] arr[ ..<-1] == arr[ ..sizeof(arr)+0] arr[ ..<-2] == arr[ ..sizeof(arr)+1] On the other hand, I don't think it matters much as long as it's defined. But to be consistent with arr[-1] the first one might be a tad better.

2 1

Jump to page:

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