Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

pike project bounty
by Martin Bähr 16 Dec '06

16 Dec '06

hi, money from the book sales is slowly coming in, together with surplus from conference fees and pledged donations we will soon reach 1000 euro. we have not set up any bounties and i suspect that doing so, as well as finding candidates to implement the projects will take a while. until then we need a place where this money can be stored safely with a trustworthy person. a suitable account must be found THIS MONTH! because i am changing employers, my current employer can not hold the money, and he also can not move it to my private account because then i would have to pay income tax on it. i can not offer to hold the money because i am changing location to often and as i do not trust internetbanking i do not have the ability to send money my account from anywhere but only to get cash out of an ATM which does not help us here. we need another (at least temporary) solution. and we need it quickly. it might also be worth looking at organizations like: https://www.pubsoft.org/ but that is ib the US whereas the money currently is in europe and i suspect that most projects will also be here. international money transfers accross currency boundaries are very expensive. bounty sites might also work but for those we need to have projects defined. suggestions, volunteers? greetings, martin.

15 45

books
by Martin Bähr 08 Dec '06

08 Dec '06

hi, btw, since we are talking about how to handle the book money, i thought i might mention that there are now only a handful of books left. does IDA want any? greetings, martin.

1 0

pike documentation is bad...
by Martin Bähr 24 Nov '06

24 Nov '06

...and i am starting to understand why. turns out that doing a tutorial with beginning programmers (first year computer science students) is really helpful. these students have no problem to understand the syntax, they where happily working with the examples and understanding how to apply them to solve their problems, but once you point them to the module reference they become lost. here is what i experienced today: .... students: we'd like to do this interface with 3d graphics. me: ok, lets take a look at GLUE, which should make this easy. we find GLUE.init() and after explaining the use of the backend, figuring out that the default is fullscreen, how to fix that, etc, we wonder what's next. me: lets try to draw something. here draw_box() looks promising: void GLUE.draw_box(float x0, float y0, float x1, float y1, array(Image.Color.Color)|Image.Color.Color c, void|array(float)|float a) students: what is this Image.Color.Color? me: lets take a look: well it's a color object. to see how to use it, we look at the create function http://pike.ida.liu.se/generated/manual/modref/ex/predef_3A_3A/Image/Color/… me: see, it takes 3 arguments, for each of the parts of a color. students diligently type: Image.Color.Color.create(255,255,255); me: oh, wait, (explaining the use of create) Image.Color.Color(255,255,255); Compiler Error: 1:Too many arguments to clone call. Compiler Error: 1:Expected: function( : object(is 200)) Compiler Error: 1:Got : function(int(255..255), int(255..255), int(255..255) : void | mixed) me: say what??? this is wierd! being creative, i try looking at Image.Color, find the description we were looking for, and use Image.Color("red"); .... can anyone see where the problem is? if you are new to pike, you lack the creativity needed to figure out how the documentation is to be interpreted. at the pike conference someone mentioned at one point that it would be useful to hide the create() function, and display it instead more prominently. actually pretty much like in Image.Color. but that is just one thing. in this example: the color type is referenced as Image.Color.Color and this reference was not really helpful in determining what you really need to do to obtain such an Image.Color.Color object. why is that? details like these are spread throughout the reference, i don't know if there are any more misleading like this one, but i now understand much better why people still complain about the documentation. beginning programmers simply get lost. for them, these issues are not obvious. so there is still a lot of work to do. it's time we get that bounty program rolling. (more on that soon in an extra message) greetings, martin.

3 2

Re: Pike 7.6.94 alpha
by bertrand.lupart＠linkeo.com 14 Nov '06

14 Nov '06

Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Probably due to stewas change: > > o Made IA32 machine code compatible with Darwin IA32 ABI. Enabled > machine code for Darwin. > > Is this something you could take a look at? Still investigating, but finally should be a problem on my side. -- Bertrand

1 0

Re: Pike 7.6.94 alpha
by bertrand.lupart＠linkeo.com 14 Nov '06

14 Nov '06

> Pike 7.6.94 alpha can be found at: > http://pike.ida.liu.se/pub/pike/alpha/7.6.94/Pike-v7.6.94.tar.gz > Compiling it on darwin ppc, and i have a new warning i didn't had with 7.6.86: ----8<----8<----8<----8<---- checking default compiler ABI... configure: WARNING: Unrecognized object file format: Mach-O object ppc ---->8---->8---->8---->8---- -- Bertrand

2 1

Pike 7.6.94 alpha
by Peter Bortas ＠ Pike developers forum 14 Nov '06

14 Nov '06

Pike 7.6.94 alpha can be found at: http://pike.ida.liu.se/pub/pike/alpha/7.6.94/Pike-v7.6.94.tar.gz Alpha because this will not be the release. There is text for one item in CHANGES missing and I need to fix a longstanding bug in the Unix installer. Changes since Pike 7.6.86 ---------------------------------------------------------------------- Changes in Pike: o Added conversion from Gmp.mpz objects to Gmp.bignum when cast to int. o Added timeout to Image.PS. Now kills the ghostscript process if it hasn't returned after 30s. o Added GL 1.2 and 1.3 constants. o Added possibility to set offset and stride when creating textures from memory objects in GL. o Fixed CMYK calculation in Image.Image. o Added adjusted_cmyk to Image.Image and use it when decoding with Image.PS. o Now handles more eps images internally in Image.PS without spawning ghostscript. o Added Standards.IIM that handles IPTC IPTC Information Interchange Model data in JPEG or Postscript images created with PhotoShop. o Added support for little endian TIFFs. o Added support for TIFF to Image.Dims. o Changed HTTP.Query to close connections explicitly. o Improved Parser.XML.Validating. o More paranoid checks of image headers when using Image.AVS. o Fixes to make describe_value work as usual in the free pass of the gc, so that e.g. sprintf("%O",...) behave well when called from destroy(). o Fixed truncated field names in ODBC. o Fixed masking of file positions larger than 2 GiB on 64-bit. o Fixed low-level parsing of HTTP headers to not reorder the headers. o Fixed an inverted error test in Mysql.set_charset. o Added set_charset and get_charset proxy functions to Sql.Sql. o Changed Protocols.HTTP.Query async_close() to care about the value returned by ponder_answer(). Fixes requests to broken servers that don't send proper results. o Fixed bad free_string() in exit_bytecode(). o Fixed an off-by-one crash when drawing alpha boxes all the way to the bottom of the image. o FIXME_SPECIFY: "mast: Backported multiset fixes." Other: o Improved Valgrind support. o Now checks the return code from win32 VirtualProtect. This breaks assembler optimized builds on Windows. It never worked in the first place, but used to fail silently, so this is better. This has been fixed in 7.7 by using another heap manager, but it has not been decided if it should be be backported. o Adjusted array growth policy in array_insert to double the size instead of growing with approximately one eighth of the size. This to ensure O(1) time complexity and lessen fragmentation. (This affects ADT.Sequence._insert_element and ADT.CircularList._insert_element.) o Fixed support for UnixODBC. o Made IA32 machine code compatible with Darwin IA32 ABI. Enabled machine code for Darwin. Build fixes: o Support GNU Java (GCJ) o Did away with the use of the undocumented internal MS win32 CRT functions __loctotime_t and __dtoxmode. o Fixed typo that caused the configure script to search for lots of nonapplicable include dirs on windows. o Backported new INT_TYPE_{ADD,NEG}_OVERFLOW implementation from 7.7. The old one does not work with GCC 4.1. o Fixed problem where mysql_character_set_name exists in mysql.h but not in the lib for some old mysql clients.

1 0

embedding pike
by Martin Bähr 13 Nov '06

13 Nov '06

hi, during the conference it was mentioned that pike embedding support is not done yet because there are still namespace issues? what does it take to fix those? is it anything more than renaming all the functions (prefixing them with "pike_")? greetings, martin.

7 12

<if> inside <ul> in pike site?
by Martin Bähr 11 Nov '06

11 Nov '06

hi, does anyone have a clue why an <if> inside the <ul> block on /download/index.xml never shows? <if variable='var.winstable'>works as expected</if> <ul> <li><a href="/download/pub/pike/latest-stable/"> <b>Latest stable binary version</b> (&var.stable;)</a><br/> Binaries for the most recent release are made available as we manage to produce and quality control them. Usually made for at least Linux x86, Linux ppc and Solaris sparc. For more info, read the <a href="notes/&var.stable;.xml">release notes</a>.</li> <if variable='var.winstable'>this if seems never true</if> </ul> if that would work then the simple existance of /download/currentwinstable.txt could determine wether a seperate "windows" paragraph is visible or not greetings, martin.

5 5

bugs in master with -rt
by Tobias S. Josefowitz 11 Nov '06

11 Nov '06

In master.pike, namely in "string describe_backtrace(mixed trace, void|int linewidth)" it is assumed that if (arrayp(something)) { array a = [array]something; } is a safe operation. However, if Pike is started with -rt, this provides us with neat "describe_backtrace(): Soft cast failed. Expected array, got object(is 11)" errors. The object that pretends to be an array is a backtrace_frame, at least in the cases that occured to me. PS: I forgot my password for the bugcruncher, and can't create new accounts because of a mysterious "Could not create LysKOM identity"...

1 0

invalid struct * callable?
by H. William Welliver III 10 Nov '06

10 Nov '06

I'm working on my Objective C bridge, and I'm running into a problem that doesn't make a whole lot of sense to me. I have an object that I am calling f_index() on to see if a function exists in the object, and while f_index() is returning an svalue that says it has a function in it, the callable seems to be invalid, as accessing things in it causes a segfault. I think I'm adding refs as appropriate to the program and object that the function lives in. Do I need to do anything to the function itself (which is in an object derived from a pure pike class)? push_object(pobject); push_text(funname); f_index(2); free(funname); if(Pike_sp[-1].type == PIKE_T_FUNCTION) // jackpot! { fun = Pike_sp[-1].u.efun; printf("-> get_func_by_selector(%s)\n", fun->name->str); // we segfault here add_ref(fun); pop_stack(); return fun; } else return 0; It might also be worth noting that I'm creating instances of my class using the following: struct object * pobject; pobject = clone_object(prog, 0); add_ref(pobject); object_setInstanceVariable(obj, "pobject", pobject);

1 0

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