Pike-devel November 2003

pike-devel@lists.lysator.liu.se

7 participants
35 discussions

Image.SSL?
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 04 May '04

04 May '04

Pike v7.3 release 62 running Hilfe v3.5 (Incremental Pike Frontend) > Image.gurkburk; /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/handshake.pike:978:Index 'decode_certificate' not present in module 'X509'. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:26:Error finding program /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:26:Illegal program pointer. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:35:Illegal program pointer. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:36:Illegal program pointer. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:37:Illegal program pointer. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:41:No inherit or surrounding class alert. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:42:No inherit or surrounding class urgent. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:43:No inherit or surrounding class application. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:46:No inherit or surrounding class handshake. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:123:No inherit or surrounding class alert. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/connection.pike:126:No inherit or surrounding class urgent. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:9:Error finding program /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:9:Illegal program pointer. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:120:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:147:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:364:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:397:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:402:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:410:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:420:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:425:Must return a value for a non-void function. /pike/home/marcus/Pike/7.3/lib/modules/SSL.pmod/sslfile.pike:434:Must return a value for a non-void function. Compiler Error: 1:Index 'gurkburk' not present in module 'Image'. > Two questions: 1) Why is it trying to load SSL.pmod? 2) Why is it failing?

12 137

More about ADTs
by Peta, jo det �r jag ＠ Pike developers forum 04 May '04

04 May '04

I've made som changes and here is a new suggestion for a common interface of the new ADTs. Common API for new ADTs in Pike 1. Introduction This document describes a common platform for new ADTs in pike to stand on. The purpose of the platform is to make the new ADTs as flexible as possible and possible to use together with generic algorithms. The base of the platform is the Collection concept, being the base concepts of all the ADTs, and the Iterator concept making it possible to iterate over collections without knowing the underlying structure. Besides the two base concepts this document also describes a few sub-concepts that are related to the two base concepts according to the two figures below. Figur 1 Collection concepts Collection |-----------> Ordered Collection | | | |--------> Sequence | |--------> Ordered Set <------| | |--------> Ordered Map <--| | |----> Map --------------------------------------| | |----> Set ------------------------------------------| Figur 2 Interface concepts Iterator -------> Ordered Iterator 2. Collection concepts 2.1. Collection Collection is the base concept of all the ADTs. The reason it is called collection is that all the ADTs in the library is in some way a collection of items. To implement a collection the following methods must be implemented iterator _get_iterator() Return an iterator for this ADT positioned at the first item in the ADT. int _sizeof() Return the current size of the ADT. Return -1 if the size could not be decided or is truly unlimited. array _values() Return an array with the values in the ADT. int _has_value(mixed value) Returns 1 if value is in the value domain of collection, or 0 (zero) if not found int _equal(mixed coll) Decide if the collection coll and this collection contains the same elements, an if it is important, in the same order. string _sprintf(int conversion_type, mapping(string:int)|void params) Present the collection in a human readable way. For more information see _sprintf in the pike manual. int is_empty() Return 0 if the ADT do has elements. int max_size() Return the maximal size of the ADT if there is any, otherwise -1. void clear() Clear the ADT. iterator first() Return an iterator for this ADT positioned at the first item in the ADT, same as _get_iterator(). iterator last() Return an iterator for this ADT positioned at the last item in the ADT. 2.2. Set Set is a collection containing any number of items but only one of each item. It is a sub-concept of Collection and must thereby besides implementing the methods below also implements the methods in Collections. int '[](mixed item) Return 1 if the item could be found in the set, 0 if it couldn't int '[]=(mixed item, int exist) Add the item to the set if exist is true remove the item if exist is false. iterator get_iterator(mixed item) Get an iterator for this ADT positioned at the item or null if the item could not be found int insert(mixed item) Add the item to the set if it isn't a part of the set. Return true if the item was added, else false. mixed delete(mixed item) Remove the item from the set. If the item was removed it will be returned otherwise a 0 zero_type is returned. multiset cast("multiset") The set should at least be able to cast to a multiset, additional castings are optional. 2.3. Map A map is a data structure that allows you to associate a key with one or more values and then quickly retrieve those values using the key. To implement a Map the ADT must have all the methods in this concept and in the Collection concept. mixed '[](mixed key) Return the item associated with the key if it could be found, 0 if it couldn't mixed '[]=(mixed key, mixed item) If there is an item with the key key then the associated item will be overwritten with the supplied item. If there is no key in the map a new key-item pair will be added. iterator get_iterator(mixed key) Get an iterator for this ADT positioned at the key or null if the key could not be found. mixed insert(mixed key, mixed item) If the key doesn't exist or duplicates are allowed, associate the value with the key and return 0, otherwise don't modify the map and return the current value associated with the key. mixed delete(mixed key) Remove the pair with the key key. Return the keys value if it was removed, if the key could not be removed return zero_type. mapping cast("mapping") The map should at leas be able to cast to a mapping, additional castings are optional. 2.4. OrderedCollection An OrderedCollection is a collection that has indices that could be used to find the values and the indices are strictly ordered is some way. Any type could be used as an index if it satisfies a few rules. See Index for more information. There is also nothing that prevents the use of the values as indices as long as the value satisfies the rules for an Index. int _has_index(int index) Returns 1 if index is in the index domain of collection, or 0 (zero) if not found array _indices() Return an array with the indices of the collection. 2.5. Sequence A sequence is a sub-concept of an Ordered Collection. It is a linear collection that allows index-based access and automatically expands to accommodate new elements. A vector is a good example. mixed '[](int ind) Return the item at index ind in the sequence. Throw an error if ind is out of range. mixed '[]=(int ind, mixed item) Set the index ind to be item. Throw an error if ind is out of range int _search(mixed item, void|int start) Return the index of the first item in the sequence with the index start or higher that match the item item. -1 if no object was found. Throw an error if start is out of range. void insert(index ind, mixed item) Insert an item in the sequence at the index ind. The size of the sequence is increased by one and the items at index and above have their indices increases by one. Throw an error if ind is out of range. int(0..1) delete(mixed item) Remove the first value that are equal to item from the sequence. Return 1 if a item was removed, otherwise 0; void add(mixed item) Add the object item as fast as possible to the sequence. int delete_at(int ind) Remove the item at the index ind. The size of the sequence is decreased by one and the items above ind have their indices decreases by one. Return 0 if the removal failed. Throw an error if ind is out of range. iterator get_iterator(int ind) Get an iterator for this ADT positioned at the index ind. Throw an error if ind is out of range. array cast("array") The sequence should at least be able to cast to an array, additional castings are optional. 2.6. OrderedMap An OrderedMap is a map where the keys are orderable and the iterator belonging to an OrderedMap will traverse the values in that order. 2.7. OrderedSet An OrderedSet is a set were the values are orderable and the iterator belonging to an OrderedSet will traverse the values in that order. 3. Iterator concepts 3.1. Iterator The iterator concept does not differ much from the present day iterator. Only a few new methods are added to make it possible to step backwards and compare iterators. int(01) '!() Should return 0 (zero) when not at end of collection, and 1 at end of collection void '+=(int n) Should advance the specified number of steps iterator '-=(int n) Move the iterator n steps backwards int '==(iterator iter) Return true if the two iterators is pointing to the same object. Throw an error if the two iterators belong to different collections. mixed index() Should return the current index. mixed value() Should return the current value int has_previous() Return true if the iterator can move one step backwards. int has_next() Return true if the iterator can move one step forwards. It have the same use as '!(). collection get_collection() Return the collection this iterator iterates over. Optional void set_value(mixed value) Set the value of this iterator. This method should only be available if it is possible to set the value via an iterator. Optional void add(mixed value) Add a new item to the collection after the item the iterator currently is pointing at. This method should only be available if it is possible to add entries via the iterator Optional mixed remove() Remove the item the iterator currently is pointing at and move to the next item. This method should only be available if it is possible to remove entries via the iterator 3.2. OrderedIterator An OrderedIterator is an iterator working on an OrderedCollection. It has two characteristics, first it traverse the collection in the same order each time it is traversed, if the there hasn't been any changes in the collection, beginning with the item with the lowest index and ending with the item with the highest index. Secondly it is possibly to say that an iterator is less then or greater then another iterator. int(0..1) '<(OrderedIterator iter) Return 1 if iter is positioned after this iterator, otherwise 0. Throw an error if the two iterators belong to different collections. Int(0..1) '>(OrderedIterator iter) Return 1 if iter is positioned before this iterator otherwise 0. Throw an error if the two iterators belong to different collections. 4. Index If a type could be used as an index in an OrderedCollection then it must be possible to use the following operations on it. '== If the two indexes a and b is equal it should return 1 otherwise 0. The following rules must also be satisfied. a == a must be true a == b implies b == a !(a == b) implies a != b a == b and b == c implies a == c '< If the index a is ordered lower than b it should return 1 otherwise 0. The following rules must also be satisfied. a < a must be false a < b implies !(b < a) a < b implies (b > a) a < b and b < c implies a < c '> If the index a is ordered higher than b it should return 1 otherwise 0. The following rules must also be satisfied. a > a must be false a > b implies !(b > a) a > b implies b < a a > b and b > c implies a > c

11 73

SDL
by David Hedbor ＠ Pike developers forum 04 May '04

04 May '04

I have now implemented and checked in SDL.Surface->set_pixel and get_pixel methods. Note that they do no boundary checking so if you write outside the surface... Well, go figure. I could add it but I'd rather avoid any checks I can for performance reasons...

6 18

Starting new pike processes from the testsuite
by Niels M�ller (ny flexiblare br�stkorg) ＠ Pike (-) developers forum 24 Feb '04

24 Feb '04

What's the recommended way of starting separate processes (which are Pike programs) from the testsuite? I want to make a test case for the SSL code, by starting a https process using the SSL.pmod/https.pike program (which I'm not sure it really belongs in the module tree) or some similar code, and then use the client code in the url/http modules to connect to it.

9 35

module documentation
by Bill Welliver 30 Nov '03

30 Nov '03

I've run into a problem with building module documentation outside the pike tree: when a documentation build directory is within the documentation source directory, you end up with a recursion loop. this is because extract_autodoc creates a parallel tree inside of the documentation build directory, and once the extractor descends into the documentation build directory, it never reaches the end of the directories to recurse. The problem came up because autodoc markup is not extracted from C/CMOD source files using the new extract targets. I wanted to add this, but ran into the problem above. As far as I can see, there are 3 avenues: 1. build documentation outside of the documentation source directory (ie the module build directory) i don't think that this is a very good option, as it only masks the problem. 2. add a check in extract_autodoc.pike to check for the problem and stop recursing into the documentation build directory this stops the problem above, but seems to create a problem with duplicate documentation for the module in question (it ends with an error to this effect). 3. add a separate target that will extract documentation for files specified in the makefile, as say AUTODOC_C_INPUT or something, then extract the pike autodoc as normal. this would require extract_autodoc to be modified to be able to extract from a source file, rather than a directory. Anyone have any constructive thoughts about the problem in general and a solution to it? Bill

1 0

Checking threads on ppc
by Martin Stjernholm, Roxen IS ＠ Pike developers forum 25 Nov '03

25 Nov '03

When ppc machine code is used, this program won't terminate: int do_work = 1, rounds; void work() { while (do_work) { rounds++; } } int main() { for (int i = 0; i < 5; i++) Thread.thread_create (work); sleep (10); do_work = 0; sleep (1); werror ("rounds: %d\n", rounds); } The reason is that it uses OPCODE_INLINE_BRANCH and doesn't generate the appropriate calls to check_threads_etc() on backward jumps after branch opcodes. (Normally the opcodes do that themselves since they have the address to jump to.)

2 3

Re: A bug(?) in lfun::`[]() handling
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 25 Nov '03

25 Nov '03

> I want to parse something (from specific subset) that specified inside of > [], and pass control to default `[]() operator when this something doesn't > fit to specific rules. But you can't pass something to the default [] operator which doesn't fit to the rules of the default [] operator. So it's your code which is faulty. > But I wonder why `->() was called... It shouldn't be there (at least I see > no reason why it should). The default [] implementation uses the -> implementation to save code duplication, since they have the same semantics (on objects). / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2003-11-25 21:31: >Subject: Re: A bug(?) in lfun::`[]() handling >-------------------------------------------------------------------- >On Tue, Nov 25, 2003 at 09:05:03PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote: > >> there, although I'm not sure what. What semantics did you intend for >> your [] operator? > > I want to parse something (from specific subset) that specified inside of > [], and pass control to default `[]() operator when this something doesn't > fit to specific rules. > > But I wonder why `->() was called... It shouldn't be there (at least I see > no reason why it should). > >Regards, >/Al > > > / Brevbäraren >

1 0

A bug(?) in lfun::`[]() handling
by Alexander Demenshin 25 Nov '03

25 Nov '03

Hi, Doing some experiments (Pike 7.4.28)... So: ---snip--- class Parent { mixed `[](mixed ... args) { Stdio.stderr->write("Called `[](%O) in %O: %O\n", args, this, ::`[](@args)); return ::`[](@args); } } class Child { inherit Parent; } int main(int argc, array(string)argv) { Child obj = Child(); mixed val; val = obj[-1..1]; // Just in case - optimizer will cut the code when "val =" is removed. } ---snip--- The attempt to execute gives: Bad argument 1 to ::->(). Expected string Unknown program: ::->(-1,1) object.c:2105: object.c:2105()->()(-1,1) inh2.pike:5: inh2()->Child()->](-1,1) inh2.pike:20: inh2()->main(1,({"/home/aldem/src/pike/inh2.pike"})) I don't have any definition of `->() nor any references to it... And no references in docs that `->() and `[]() are equivalent... In fact, inheritance doesn't matter - it is just my standard template for test cases... Substitute Child to Parent and the error will be exactly the same. Not sure if problem exists with 7.5 or 7.4-cvs version - didn't check it out (yet)... Regards, /Al

2 1

Bootstraping pike-cvs and stripped down source dist
by Alexander Demenshin 25 Nov '03

25 Nov '03

Hi, Is there any way to build pike-cvs _without_ working Pike installed? And second question... Some time ago someone posted here a minimum set of of modules which are really necessary to install/run Pike, so the question is - is it possible to "strip" all unnecessary modules from the source tree so they won't be compiled at all? Will simply removal of modules from the source work? For those who wonder why - I just want to release an application (naturally, written in Pike), but I don't want to force users to install full version of Pike (they don't need it at all but to run my app, and I know exactly what I (don't) use). Regards, /Al

3 2

fake_dynamic_load.pike
by Martin Nilsson (saturator) ＠ Pike (-) developers forum 22 Nov '03

22 Nov '03

When looking over the bin folder manifest I found that fake_dynamic_load.pike isn't documented. What is it for and when is it used?

4 7

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 November 2003