Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

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

Assumed .pike
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 28 Dec '07

28 Dec '07

If .pike is omitted when declaring a script to run, Pike will add this automatically. It will however not update the argv array. Is this the behaviour you would expect? Example. foo.pike: void main(int n, array args) { write("%O\n", args); } $ pike foo bar ({ /* 2 elements */ "/home/nilsson/foo", "bar" })

3 2

pcre bundled with pike 7.8
by H. William Welliver III 20 Dec '07

20 Dec '07

I'm not sure if this was discussed previously, but would there be any possibility of bundling pcre with pike 7.8, or at least compiling with it on windows? Just wondering... bill

3 7

external module building under 7.7
by H. William Welliver III 15 Dec '07

15 Dec '07

I've been playing around with external module building under Pike 7.7, and I think that most of the difficulty involves propagated_variables. There's a propagated_variables file that gets installed in include/pike, but it seems that the macro that actually reads this file only looks for it in the current directory. I think I understand that rationale when compiling within the source tree, but think there needs to be a behavior that checks for the file in the installed headers directory too. The question for those more knowledgeable in this magic is: does it seem reasonable to check in the installed headers directory first (most likely $BUILD_BASE, I think), then in the current directory for all situations or would that have an undesirable effect when compiling within the Pike source tree?

3 2

pike on iphone
by H. William Welliver III 01 Dec '07

01 Dec '07

I've been playing around with the idea of getting pike to run on apple embedded devices. I don't have an iphone, but I do have an ipod touch, which is essentially the same thing. I managed to get gmp and nettle to compile, but without assembler. It's not clear at this point whether the problem is due to incorrect detection of the assembly type, or some other problem. Pike's configure script seems to run correctly, but my current problem is that the current iphone toolchain uses LLVM-GCC, which is pretty buggy, and it crashes while compiling multiset.c. I'm not sure whether I want to go through the effort of trying to fix that problem or if using straight gcc would work better (assuming that gcc generates arm objects for darwin). Anyhow, I thought that some out there might be interested in this. Bill

1 0

Nettle
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 27 Nov '07

27 Nov '07

Pike v7.6 release 117 running Hilfe v3.5 (Incremental Pike Frontend) > Crypto.DES3()->set_encrypt_key("\x01\x23\x45\x67\x89\xab\xcd\xef"+"\x01"*8); DES3_INFO: Key is weak. src/post_modules/Nettle/cipher.cmod:785: Nettle.DES3_State()->set_encrypt_key("\1#Eg\211«Íï\1\1\1\1\1\1\1\1") HilfeInput:1: HilfeInput()->___HilfeWrapper() > Well, never you mind! I need to use this particular key for testing, and don't care that it's weak (it's just a test key anyway). The autodoc says /*! @decl CipherState set_encrypt_key(string key, void|int force) but that doesn't seem to work either: > Crypto.DES3()->set_encrypt_key("\x01\x23\x45\x67\x89\xab\xcd\xef"+"\x01"*8, 1); Compiler Error: 1:Too many arguments to set_encrypt_key. Compiler Error: 1:Expected: function(string : { this_program = object(implements 65740) }) Compiler Error: 1:Got : function(string, int(1..1) : void | mixed) > What gives?

1 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