Pike-devel April 2009

pike-devel@lists.lysator.liu.se

5 participants
9 discussions

nabble.com
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 28 Apr '09

28 Apr '09

Happened to notice the list archive at nabble.com: http://www.nabble.com/Pike---Dev-f14138.html Grubba is apparently very talkative, although he talks to himself a lot too. ;)

3 2

Call for new stable
by Peter Bortas ＠ Pike developers forum 21 Apr '09

21 Apr '09

It's time to package the accumulated 7.8 fixes. Let me know if you have anything outstanding in 7.8 right now that needs to be fixed, or I will try to package and ship whats in CVS ASAP.

1 0

get_dir() problem
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 21 Apr '09

21 Apr '09

Fixed.

2 1

get_dir() problem
by Peter Bortas ＠ Pike developers forum 21 Apr '09

21 Apr '09

Something is fishy with get_dir(). I had a directory with 232 directories in, where get_dir() returned an empty array. Adding a directory fixed it to return the correct result. ls had no problems, and when tracing get_dir() syscalls it looks like it gets the correct things back: Non-working;: open(".", O_RDONLY) = 7 fpathconf(7, _PC_NAME_MAX) = 255 fcntl(7, F_SETFD, 0x00000001) = 0 fstat(7, 0xFFFFFD7FFFDF9AB0) = 0 getdents(7, 0xFFFFFD7FFEEE4000, 8192) = 8168 getdents(7, 0xFFFFFD7FFEEE4000, 8192) = 1160 getdents(7, 0xFFFFFD7FFEEE4000, 8192) = 0 close(7) = 0 Working after adding dirs: open(".", O_RDONLY) = 7 fpathconf(7, _PC_NAME_MAX) = 255 fcntl(7, F_SETFD, 0x00000001) = 0 fstat(7, 0xFFFFFD7FFFDF9AB0) = 0 getdents(7, 0xFFFFFD7FFEEE4000, 8192) = 8176 getdents(7, 0xFFFFFD7FFEEE4000, 8192) = 1224 getdents(7, 0xFFFFFD7FFEEE4000, 8192) = 0 close(7) = 0 root:~# /usr/local/bin/pike --dumpversion 7.8.116 root:~# uname -a SunOS ministore 5.11 snv_101b i86pc i386 i86pc

3 9

get_dir() problem
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 21 Apr '09

21 Apr '09

I see the bug...

1 0

trademark question
by Martin Bähr 21 Apr '09

21 Apr '09

hi, i am reviewing the pike entry on wikipedia and noticed that the logo image lacks clear license information. while trying to find out what the actual license is i found that there is no clear information on the pike website either. i think it would be helpful if http://pike.ida.liu.se/about/pike/ contained a phrase like: the pike name and logo are registered trademarks of IDA. i would also like to clarify the license of the logo images on http://pike.ida.liu.se/download/logotype/ i believe there is no problem with making them gpl or mpl since they are protected by a trademark anyways. are there any issues with adding these clarifications on the pike site? greetings, martin.

4 6

Big endian twos complement
by Coen Schalkwijk 20 Apr '09

20 Apr '09

I'm giving OpenID a try and need to get the big endian two's complement of a large (if not) number (a/the default Diffie-Hellman 'p' value) how do I do that in Pike? I've tried to figure it out myself, but I get a bit lost between all the definitions. Thanks in advance! 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 4

multiset fix backported
by Peter Bortas ＠ Pike developers forum 08 Apr '09

08 Apr '09

I just backported the multiset fix to 7.6 since we are getting it by it on a regular basis. The test suite runs fine even with TEST_MULTISET, but someone more familiar with the code should probably have a look to make sure I didn't mess something up.

3 4

(semi-)multicore support?
by Arjan van Staalduijnen 02 Apr '09

02 Apr '09

Hi, Unfortunately we all still have to do without multicore or multi-cpu support in pike. Even though I don't know how the stuff works at the lowest levels I am aware it has something to do with the way pike handles it's variable structures internally, and it is definitely not a simple thing to change while maintaining a good performance at it. My curiousity is about something different, but related to having some limited multicore support. I vaguely remember hearing, or having read something somewhere about the way pike interacts with libmysql. My memory might be fooled by wishful thinking, so I might be completely wrong. I believe I understood pike is able to release some restrictions at the moment it knows it enters the code for libmysql. This would be the case because it would be benificial for performance; the mysql library would be able to switch to a mode where it could manage it's memory more freely, or where it would be able to run on a different core/cpu. If that is possible, I wonder if libmysql is the only C-library doing this kind of trick, or if other libraries (especially the CPU and memory intensive ones) are doing this kind of trick too. Image libraries, zlib and any C-library doing lots of 'library-local' memory operations (libxslt) or any library doing CPU intensive stuff seem really nice candidates... Am I wrong at what I think pike is doing? If not, is this just for libmysql or are other modules doing this too? If I was wrong, is what I was thinking technically possible, or am I just being too idealistic? Regards, Arjan __________________________________________________________ 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. __________________________________________________________

10 18

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 April 2009