Pike-devel

pike-devel@lists.lysator.liu.se

1 participants
3045 discussions

pike-svn repo import into git
by Martin Bähr 23 Feb '08

23 Feb '08

hi, importing the pike-svn repo into git took 3 days. git-svn seems to have some issues there, as the process got slower and slower (and in the end git-svn had more than 300MB in ram (allocated 1GB)) the resulting repo had 178645 objects and a size of 1178MB. git-svn allocates another 1.5GB for statusinformation on each branch. (and because tags are branches, the 1729 tags result in as many branches) however, after packing, the resulting repo ocupies a mere 44MB!!! that alone is a good reason for me to use git, as it it gives me the whole repo in the same space as the checkout of a single revision in svn. you can clone this repo from http://www.iaeste.at/~mbaehr/pike-svn.git the svn import info is removed from that repo. when we switch to svn i'll try to make a repo available that contains the svn info to spare anyone else who wants ot use git-svn a 3day import. greetings, martin.

5 9

debian package of pike (and caudium)
by Henrik Andreasson 23 Feb '08

23 Feb '08

Hi! How is it going with the debian packages of pike, anything I can to to help? The package is still owned by debian-qa-team maybe a new version that adopts the package would be good? Shamless request: I'm going to take over the caudium package but I'm not yet a debian developer so maybe somebody on the list could help me in the beginning with the uploads? //Henrik Andreasson "kinneh"

8 9

ASN.1
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 15 Feb '08

15 Feb '08

I just saw that Crypto.SHA1 and Crypto.SHA256 are missing the asn1_id method. Looking at the old crypto library the id should be /* * SHA1 OBJECT IDENTIFIER ::= { * iso(1) identified-organization(3) oiw(14) secsig(3) * algorithm(2) 26 * } * * 0x2b0e 0302 1a */ static char sha_id[] = { 0x2b, 0x0e, 0x03, 0x02, 0x1a, }; or > (string)({ 0x2b, 0x0e, 0x03, 0x02, 0x1a }); (1) Result: "+\16\3\2\32" but actually encoding it from start generates > Standards.ASN1.Types.Identifier(1,3,14,3,2,26)->get_der(); (2) Result: "\6\5+\16\3\2\32" Why are the leading bytes missing/added? Similar discrepancies can be seen for MD2/MD4/MD5. SHA256 has an PKCS id (2.16.840.1.101.3.4.0.1) that should be added to that algorithm, if we can only figure out if the two extra bytes at the beginning should be there.

2 3

Sprintf wrap removes space
by C. Schalkwijk 07 Feb '08

07 Feb '08

Thanks for the leads, but the problem with the proposed solution is that the code wrapping the text is used in a generic way. The code processes fields containing data. It wraps text in such a way that it fits the field's dimensions, without word breaks! Therefore I need the text to remain absolutely unchanged (other than inserting an EOL) and still prevent word breaks. In my opinion, removing characters from a string (when not requested) is faulty behaviour and should not occur. 'possibly skipping or adding spaces' is not desired. Greetings Coen __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

4 11

sprintf wrap removes space
by C. Schalkwijk 04 Feb '08

04 Feb '08

the following string: "\6\6\6\6\6\6\6\6\6\6\6 \3\6\6" results in: "\6\n\6\n\6\n\6\n\6\n\6\n\6\n\6\n\6\n\6\n*\6\n\3*\n\6\n\6" when using: "%-=*s" (width set to 1 (one)) While I want it to be: "\6\n\6\n\6\n\6\n\6\n\6\n\6\n\6\n\6\n\6\n*\6\n \n\3*\n\6\n\6" What am I doing wrong? Thanks in advance! __________________________________________________________ Deze e-mail en de inhoud is vertrouwelijk en uitsluitend bestemd voor de geadresseerde(n). Indien u niet de geadresseerde bent van deze e-mail verzoeken wij u dit direct door te geven aan de verzender door middel van een reply e-mail en de ontvangen e-mail uit uw systemen te verwijderen. Als u geen geadresseerde bent, is het niet toegestaan om kennis te nemen van de inhoud, deze te kopieren, te verspreiden, bekend te maken aan derden noch anderszins te gebruiken. The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Please notify us immediately if you have received it in error by reply e-mail and then delete this message from your system. __________________________________________________________

3 5

Calendar: Weeks spanning years
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 29 Jan '08

29 Jan '08

I'm fixing a whole set of bugs regarding weeks spanning year ends (the week year, wy, didn't get propagated correctly in all cases when converting between months, weeks, days etc). A tricky case is this: > Calendar.ISO.Week(2008,1)->set_size(Calendar.ISO.Day()); (1) Result: Day(Mon 31 Dec 2008) > Calendar.ISO.Week(2008,1)->set_size(Calendar.ISO.Day())->format_ymd(); (2) Result: "2007-12-31" > Calendar.ISO.Week(2008,1)->set_size(Calendar.ISO.Day())->year_no(); (3) Result: 2008 (2007-12-31 is the Monday of the first week of 2008.) Note the bogus year in result (1). format_ymd however handles it correctly due to a special check of the year day, yd: sprintf("%04d-%02d-%02d",((yd < 1)?y-1:y),m,md) Fixing _sprintf to do the same thing means putting the same special check into YMD.year_name. But what about year_no that returns 2008? Although the whole week belongs to 2008, I expect to get 2007 for the first day of it. Looking at it that way it seems better to ensure yd > 0 always, so that the year is normalized. However, there is obviously an intention behind the current behavior when yd can be <= 0, so that's why I ask.

3 6

Mach
by Magnus Holmgren, exim.org ＠ Pike developers forum 27 Jan '08

27 Jan '08

I just got word that Pike 7.6.112 fails to build with the Mach development library version 1.3.99 installed. This is because src/threads.c refers to task_thread_times_info_data_t if defined(HAVE_MACH_TASK_INFO_H), but <mach/task_info.h> doesn't #include <mach/message.h> containing the definition. Questions are implicit.

1 0

hash_value
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 14 Jan '08

14 Jan '08

Is this a problem? > hash_value(0); (1) Result: 0 > hash_value(Math.inf); (2) Result: 0 > hash_value(Math.nan); (3) Result: 0

2 2

7.6 release plans?
by H. William Welliver III 07 Jan '08

07 Jan '08

Hi All, I was wondering if there were any plans to do a new 7.6 release in the near future. There's a bug that's critical for me in the .112 Mysql module that causes a segfault, that's been fixed in 7.6 CVS. Because of this, I was thinking about holding off on a release on my end if a new pike version was looming on the horizon. If not, that's okay, too, I can try to come up with a workaround. Bill

4 8

Unused variable warnings
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 07 Jan '08

07 Jan '08

I'm not sure all the new warnings are good, at least not as default. In the case of void f(string filename) { } there might not be a choice of removing the argument. In the case of e.g. foreach(my_mapping; string name; string value) werror("%O\n", value); the unused name-variable provides possibly helpful documentation. I think what you will see in practice is that programmers will do foreach(my_mapping;; string value) werror("%O\n", value); and not foreach(my_mapping; string name; string value) { name; werror("%O\n", value); } resulting in a codebase that is harder to work with and extend.

9 10

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