Pike-devel February 2011

pike-devel@lists.lysator.liu.se

5 participants
5 discussions

CritBit-Tree implementation for pike
by Tobias S. Josefowitz 03 Mar '11

03 Mar '11

We have been working on a CritBit tree implementation for pike. We would like to get it upstream, however we have made a few changes elsewhere that may need discussion: precompile.pike templating: we added a simple template support to precompile.pike. It basically replaces a set of identifiers in the template file before precompilation. The syntax is admittedly not very beautiful. Autodoc to support global paths in AUTODOC_SRC_IN: we could not figure out how to make the autodoc generator to extract docs from several .cmod files without the AUTODOC_SRC_IN feature applied on the generated .c-files with absolute paths. You can check it out using git from http://fortranland.com/git/pike. The branch is called critbit. We have not done any testing on non x86 machines. It would be nice if someone could run the testsuite on some big endian machine. Also, we only compiled on linux machines. There might be problems on other environments because of the gcc intrinsics we are using for prefix searches. Currently there are trees supporting float, integers and pike strings and two derived types for ipv4 ip addresses and date objects. The lookup, insert and delete operations are comparable in speed to pike mappings (1.X slower in our tests). In worst case scenario critbit trees can be slow in insert and lookup (e.g. keys like "a"*i). However, critbit trees should be more memory efficient in many cases because of the mapping overhead. Also, they support several operations that mappings don't offer, namely, iteration in lexicographical order, range lookup and finding biggest/smallest index, etc. We have written quite extensive tests and a complete documentation, which you can find at http://fortranland.com/refdoc/modref/ex/predef_3A_3A/ADT/CritBit.html Any hints, suggestions, bugreports and comments are welcome. arne and tobias

3 35

Documentation diff
by Matthew Clarke 03 Mar '11

03 Mar '11

Hi Please find attached some documentation for Pike's SDL module. I commented out the declaration of the SDL_Surface variable at the head of the PIKEFUN for SDL.set_video_mode() and everything still worked. I don't think it gets used, but is redeclared inside the following if...else statement. Thanks :)

2 1

configure and defines
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 26 Feb '11

26 Feb '11

Perhpas more a philisophical question, but do we really need configure tests for .h file defines. I just saw masts commit of testing for the existance of FIELD_TYPE_BIT and then doing #ifdef HAVE_FIELD_TYPE_BIT case FIELD_TYPE_BIT: #else case 16: #endif wouldn't no configure test and a #ifndef FIELD_TYPE_BIT #define FIELD_TYPE_BIT 16 #endif had had the same result?

3 2

Key padding AES
by Coen Schalkwijk 03 Feb '11

03 Feb '11

Hi, I have some trouble with sharing AES encrypted data between pike 7.4 and 7.8. I think this is because the 7.4 key is somehow of size 32 (whilst offering a 16 char key) and the 7.8 sticks to a key size of 16. With what is the 7.4 key padded to end up with a key sized 32? -- Met vriendelijke groet / With kind regards / mit besten Grüßen, Coen Schalkwijk Software Engineer coen.schalkwijk(a)rtl.nl <mailto:coen.schalkwijk@rtl.nl> coen(a)rtlinteractief.nl <mailto:coen@rtlinteractief.nl> +31 (0)35 671 8915

1 1

Standards.URI
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 02 Feb '11

02 Feb '11

Regarding the checking "Standards.URI: More paranoid handling of ..-segments that reach past the root.": Is the semantics of the path segment declared somewhere? If not we shouldn't probably do sanity checking/normalization of it in Standards.URI.

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 February 2011