Pike-devel January 2010

pike-devel@lists.lysator.liu.se

5 participants
12 discussions

pcvs2git.pike
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 14 Mar '10

14 Mar '10

I just tried converting Roxen 2.4: Stage Memory use Commits --------------------------------------- Import 339 MB ~17000 Raking 359 MB ~17000 Verify 361 MB ~17000 Merging 662 MB 11886 Graphing 803 MB 10897 Generate 803 MB 10897 I believe that the memory use can be reduced by using more custom datatypes (currently there are a lot of mappings generated in the merging and graphing stages). Another way to reduce the memory use is to partition the graphs in the time axis.

5 58

Re: Feedback (Re: pcvs2git.pike)
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 01 Mar '10

01 Mar '10

In svn, a change in a keyword value does not count as a change; the file does not indicate as modified and the result of "svn diff" is empty.

4 7

Gz.FIXED and Windows build
by Stephen R. van den Berg 20 Feb '10

20 Feb '10

In checking the Windows build I notice: -------- Doing tests in modules/Image/testsuite (1480 tests, pid 44356) Cond 1477:1:Index 'FIXED' not present in module Gz. Cond 1477:1:Indexed module was: Gz. Conditional 1477 (line 827) failed. Doing tests in modules/Mysql/testsuite (0 tests, pid 45592) -------- The testsuite of Gz seems to be ok, though. Any takers? -- Sincerely, Stephen R. van den Berg. "First, God created idiots. That was just for practice. Then he created school boards." -- Mark Twain

6 28

-x pv
by Mirar ＠ Pike developers forum 28 Jan '10

28 Jan '10

Could someone that know their way around GTK make pike -x pv work with GTK2?

4 6

pike problems
by Mirar ＠ Pike developers forum 21 Jan '10

21 Jan '10

How do I get the latest Pike? My Pike (7.8.393) gives me errors like /home/mirar/pike/src/interpret.c:769: Fatal error: Identifier out of range, loc->parent_identifer=-1!

5 9

Re: Feedback (Re: pcvs2git.pike)
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 11 Jan '10

11 Jan '10

Of course, having the $Id$ in the wc as well can come in handy when someone "exports" a file by simply copying it from their wc to somewhere else.

1 0

mysql charset issue
by Arne Goedeke 10 Jan '10

10 Jan '10

I observed that the Mysql module doesnt seem to reset the connection charset after a reconnect. This occurs when using something like set_charset("unicode") which triggers a "SET NAMES UTF-8". However, in case the connection is lost and the sql object reconnects automatically, it does not send the SET NAMES again. The data then comes back in latin1 and the Sql modules tries to decode them in fetch_rows(). I am using a recent pike 7.8.365, etc. Arne

3 11

eureka reinstall
by Peter Bortas ＠ Pike developers forum 07 Jan '10

07 Jan '10

Some time next week I'll upgrade eureka from Solaris Express snv_81 to whatever the latest stable OpenSolaris release is. There is no straight forward upgrade path from SXCE to OpenSolaris, so the machine will be reinstalled and the data restored from backup. That means there will be some substancial downtime for people using services on eureka. More details later.

4 13

Tabular.pike 1.8
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 05 Jan '10

05 Jan '10

+ if(String.width(out)>8) + out=string_to_utf8(out); Ok, seriously, I think for every proper use of String.width (are there any?) there are at least two improper ones. If the string is supposed to be transport encoded with UTF-8, you need to do it for _all_ strings, otherwise you will get invalid UTF-8 if the string contains characters > 127 but < 256. But who says that a "tabular" should be UTF-8 encoded anyway? For a format that has no builtin encoding indicator, transport en/decoding should be the task of the caller.

4 9

convert_1_to_0() truncating instead of skipping?
by Stephen R. van den Berg 03 Jan '10

03 Jan '10

I noticed that e.g. convert_1_to_0() (actually any conversion that goes from wider to narrower) in stralloc.c just chops off the wider part instead of actually leaving out the characters which cannot be represented in the narrower string. Is there are a reason why it is truncated instead of skipped? I'd presume that actually omitting the characters which cannot be represented would be more correct. Simply truncating them generates garbage. And, subsequently, if everyone agrees to the above, can/should I fix this? -- Sincerely, Stephen R. van den Berg. "If you make people think they're thinking, they'll love you; but if you really make them think, they'll hate you."

2 2

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 January 2010