Pike-devel March 2007

pike-devel@lists.lysator.liu.se

4 participants
17 discussions

Darwin does not do --execstack
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 12 Mar '07

12 Mar '07

For as long as I have seen Darwin machines in pikefarm, about every single file compiled (assembled?) yields output to this effect: Compiling /Users/xenofarm/beta/Pike-v7.6.104/src/module.c /usr/libexec/gcc/darwin/i386/as: I don't understand '-' flag! /usr/libexec/gcc/darwin/i386/as: I don't understand 'e' flag! /usr/libexec/gcc/darwin/i386/as: I don't understand 'x' flag! /usr/libexec/gcc/darwin/i386/as: Flag option -e has already been seen! /usr/libexec/gcc/darwin/i386/as: I don't understand 'e' flag! /usr/libexec/gcc/darwin/i386/as: I don't understand 'c' flag! /usr/libexec/gcc/darwin/i386/as: I don't understand 's' flag! /usr/libexec/gcc/darwin/i386/as: I don't understand 't' flag! /usr/libexec/gcc/darwin/i386/as: I don't understand 'a' flag! /usr/libexec/gcc/darwin/i386/as: Flag option -c has already been seen! /usr/libexec/gcc/darwin/i386/as: I don't understand 'c' flag! It would be nice with some configure test to do away with the noise.

2 1

FreeBSD 6.2 amd64 support
by Dwight Schauer 09 Mar '07

09 Mar '07

Hello. Who maintains FreeBSD support for pike? I'm trying to get Caudium 1.4.x and 1.5.x working on FreeBSD 6.2 amd64 and was told the pike is not fully supported on FreeBSD. (Please correct me if I'm wrong here, my intention is not to offend anyone). I'm willing to help out if need be on the development effort for fully supporting pike on FreeBSD. For the pike program development I've been doing on FreeBSD I've not run into any issues yet though. I'm using pike 7.6.86 for what I'm trying with Caudium. -- Dwight

2 2

DST tables
by H. William Welliver III 06 Mar '07

06 Mar '07

A few weeks ago there was talk about updated DST tables for the Calendar module, made necessary due to the upcoming changes in Daylight Savings Time here in the US. Are those available somewhere? What's needed to make the update available for those of us impacted, or is there even an impact? Bill

3 4

Syntax for restricted width string types
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 05 Mar '07

05 Mar '07

I'm considering adding support for differentiating between different width strings to the type system. This whould be useful in tracking down places where wide strings are passed where narrow strings are expected. The question is what the syntax should be. Please note that the syntax should aim at being 100% backward compatible, so adding new keywords is probably not a good idea. My suggestion: string(8) 8-bit (aka narrow) string(16) At most 16-bit wide string(32) At most 32-bit wide (default) This would allow for the possible extension of string(7) 7-bit (aka USASCII) Comments?

7 35

Syntax for restricted width string types
by Mirar ＠ Pike developers forum 05 Mar '07

05 Mar '07

non-shared and destructive, even...

1 0

Money or nothing? Trade-offs in FOSS compensation
by Martin Bähr 03 Mar '07

03 Mar '07

hi, i just found this interesting article on paying people for development. some points there may be worth considering: http://www.linux.com/article.pl?sid=07/02/23/203207 greetings, martin.

1 0

Re: Debugger
by H. William Welliver III 02 Mar '07

02 Mar '07

There is a shell of a pike debugger called unbug, but it's of limited use in these situations, as breaking and stepping is clumsy or non-existent. That said, I've fiddled with it, and it works to a certain extent for certain tasks. There is a bounty ($$$) out for implementation of step and break opcodes. If there's anyone out there with this kind of skill, do contact me. Bill On Fri, 2 Mar 2007, Saqib Saleem wrote: > Ok! And is there any way where I can tell pike to execute the .pike file > line by line so I can see whats happening. Currenlty my program is stuck in > 10 recursive loops. And trace is really throwing each and everything and so > does the werror is gonna do. > > Regards > Saqib > > > On 2/3/07 15:05, "Mirar @ Pike importmöte för mailinglistan" > <6341(a)lyskom.lysator.liu.se> wrote: > >> As I said, the werror method is usually very sufficient and you can >> print whatever you want. The "%O" format descriptor can print any >> value, so it will not crash on that. >> > > -- > Saqib Saleem > > Metro International > 3rd Floor, Interpark House > 7 Down Street > London > W1J 7AJ > United Kingdom > > Email: saqib.saleem(a)metro.lu > Telephone: +44 20 7016 1354 > Mobile: +44 78 4167 2857 > Fax: +44 20 7016 1400 > > > !DSPAM:45e83e5b117541922123026! >

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 March 2007