Pike-devel June 2009

pike-devel@lists.lysator.liu.se

7 participants
18 discussions

full MySQL 4.x support. or pike roadmap
by thomas.gusenleitner＠com-bet.com ＠ Pike developers forum 01 Mar '26

01 Mar '26

HI to all! mysql 4.x support works only with a mysql CFLAGS=-DUSE_OLD_FUNCTIONS is this correct ? are there plans to make a full 4.x support ? bye, thomas

4 4

Re: Playing music using pike and SDL.
by Martin Nilsson (lvl 60) ＠ Pike (-) developers forum 20 Jan '26

20 Jan '26

Were you not able to get any C code to play through SDL either? Does your SDL library have a mixer compiled in it (I think it is optional)?

4 3

Pike 7.8.292 beta
by Peter Bortas ＠ Pike developers forum 23 Aug '09

23 Aug '09

Roughly six months (on normal par, but double the time I'd like to see) after the first 7.8 release here is the first 7.8 update: 7.8.292 beta. Users and developers alike are encouraged to test this beta and report problems so we can have a final release as soon as possible. The source can downloaded here: http://pike.ida.liu.se/pub/pike/beta/7.8.292/Pike-v7.8.292.tar.gz A Windows binary might show up tomorrow. Changes since Pike 7.8.116 (initial 7.8 release): ---------------------------------------------------------------------- General ------- o Sql.pgsql: - Substantial documentation improvements. o Stdio.Fd_ref is deprecated and in the process of being eliminated. You have never used it before, so don't start using it now. Bugfixes -------- o Fixed bug in AGGR_ARR_EPILOGUE() (aka END_AGGREGATE_ARRAY()) that caused the empty array to always be returned if there were no unaggregated elements on the stack at END_AGGREGATE_ARRAY. You are encouraged to upgrade just for this fix since the bug creates very rare but (seemingly) random occurances of empty arrays. o Fixed multiset_delete_node to work with destructed indices. This fixes occasional bugs in various functions when there are destructed objects in indices. You are encouraged to upgrade just for this fix since the bug creates (seemingly) random crashes that are hard to reproduce and track down. o Fixed bug in the Odbc module on WIN32 where it would fail for some field-types with the error "22003:Numeric value out of range". o Sql.pgsql: - Various small fixes and performance improvements. - Fixed fully transparent UTF8/Unicode/wide string/character set support. - Fixed formatting errors in error(). o Fixed bug when seeking backwards in Gz.File. o Fixed bug in fd_stat on windows when used on a file system with a long name. o Fixed off-by-one bug in Stdio.Readline that caused a space in the last column to disappear instead of being converted to a linefeed when word wrapping is used. o Fix bug in FakeFile.read() Replaced the broken-in-multiple-ways implementation by something that actually works (hence the original enlightnening description: "fixed a bug", there is really no concise way to classify this level of brokenness). o Image.TIFF: Fixed memory leak on OOM. o Fixed crash bug in Fixed core-dump typo in yyexplain_not_implements(). o LysKOM.ProtocolTypes: Bugfix of LocalToGlobalBlock o Protected Pike_fatal() against the risk of hanging on mutexes. o Added 7.6 compat versions for RegGet{Value{,s},KeyNames}(). o Fixed memory leak in Image.Colortable. o Parser.SGML: Reinstated the class as Parser.SGML(). It inadvertedly became Parser.SGML()->SGML() in the move to a separate file. Parser.SGML.SGML is kept as a compatibility alias. o Added Pike 7.6 and earlier compat for store_constant(UNDEFINED). o Fixed race-condition causing "Lost track of child" on pikes compiled --without-threads. o Regexp.PCRE: Do not match the empty string past the end of the input. o Reduced the risk of throwing out-of-stack errors while formatting an out-of-stack backtrace. o Fixed bug that would cause sprintf's %nH to refuse all strings as too long for some values of "n" on some architectures. o Made Process.search_path() aware if Win32 and AmigaOS specifics. o Fixed bug in Protocols.HTTP.Query that dropped the last byte of a request if the server did not provide a Content-Length header. Optimizations ------------- o Fixed Filesystem._Tar.ReadFile to not gobble the whole tar entries into memory at once. o Improve performance of get_cpu_time() on OS X by avoiding a kernel trap to get the ID of the underlying system thread. o Throttle calls to task_info() on OS X since they are quite expensive. This gives a significant performance boost (>10%) on CPU-intensive applications. Extensions and New Functions ---------------------------- o Added support for specifying modifiers via a mapping to '*' in sprintf(). See the documentation for details. This support is detectable by checking for String.__HAVE_SPRINTF_STAR_MAPPING__ o Added support for generating little-endian floats with %F in sprintf(). This support is detectable by checking for String.__HAVE_SPRINTF_NEGATIVE_F__ o Sql.Sql now supports NULL values for %s-parameters. o Timeout support in win32 threads. o Made FakeFile() support getchar/gets/unread. o Added option to chown and utime that makes it possible to change the symlink instead of the target of the link. o function_name() now knows how to adjust the names of named lambdas. o Changed handling of POLLHUP for poll devices, it is now signalled on all of the callbacks. o Updated timezone data to tzdata2009c. o Added some support for the TIMESTAMP and INTERVAL datatypes to Oracle module. New modules / classes / methods added ------------------------------------- o Protocols.IPv6 Helpers for IPv6 related things. This currently only contains tools to parse and normalize addresses. (Not much more is necessary since the usual I/O interfaces support IPv6 as-is.) o Added Filesystem._Tar.extract to be able to extract many/all files in a reasonably efficient way. o Added Parser.Tabular It provides a flexible yet concise record-description language to parse character/column/delimiter-organised records. o Calendar.YMD.http_time() that knows how to handle dates according to HTTP 1.1 (RFC 2616). o Added support for GTK2 get_window() and get_pixmap(). Building and installing ----------------------- o Use the #-character as prefix and suffix for placeholders in master.pike.in instead of the currency sign, to avoid 8-bit character encoding issues. o Improved support for version bumping via both Subversion and git. o A recent stable Pike (7.8.116+) is now required to do a "make export". o The win32 installer now removes the generated master.pike on uninstall.

12 41

Pike 7.8.316 beta
by Peter Bortas ＠ Pike developers forum 11 Jul '09

11 Jul '09

New beta build, 7.8.316: http://pike.ida.liu.se/pub/pike/beta/7.8.316/Pike-v7.8.316.tar.gz Windows build: http://pike.ida.liu.se/pub/pike/beta/7.8.316/Pike-v7.8.316-win32.msi http://pike.ida.liu.se/pub/pike/beta/7.8.316/Pike-v7.8.316-win32.info (untested) If there are no valid protests I plan to release this this tomorrow.

7 42

Gmp.mpz()->gcdext()
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 26 Jun '09

26 Jun '09

Dan Nelson noted the following in the chat: 6:39 Genesys interesting. my amd64 pikefarm 7.8 fails the following test: return equal(Gmp.mpz(13)->gcdext(19), ({1, 3, -2})); 6:40 Genesys it returns ({ 1, -16, 11 }), which seems to be a correct answer if I do the math

6 20

Re: Wow, Trace++ (Re: Identifier reference index 36 out of range 0..29)
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 22 Jun '09

22 Jun '09

Looks like the only place it is used is in error.c. Remove it completely? / Martin Nilsson (Opera Mini - AFK!) Previous text: >17688274 2009-06-22 23:19 /28 lines/ Brevbäraren >Recipients: Pike (-) importmöte för mailinglistan >Comment to 17688170 >Subject: Re: Wow, Trace++ (Re: Identifier reference index 36 out of range 0..29) >-------------------------------------------------------------------- >On Mon, 22 Jun 2009, Stephen R. van den Berg wrote: > >> Henrik Grubbstr?m wrote: >>> Please update src/program.[ch] so you get the program tables dumped. >> >> This looks promising. See the new & improved full trace below. >> >>> My guess at this point is that there's some non-threadsafe code during >>> error handling in the mysql module. >> >> That's what I thought, though a casual inspection of the ALLOW() macros >> in mysql.c doesn't reveal anything significant so far. > >My main suspect is pike_threadlib.h:SWAP_IN_THREAD_IF_REQUIRED(). Try >redefining it to: > >#define SWAP_IN_THREAD_IF_REQUIRED() ASSERT_THREAD_SWAPPED_IN() > >And see if anything bites. > >> Identifier reference index 36 out of range 0..29 >> -- >> Sincerely, >> Stephen R. van den Berg. > >-- >Henrik Grubbström grubba(a)roxen.com >Roxen Internet Software AB > >(17688274) /Brevbäraren/-------------------------------------------- >

1 0

Pike 7.8.304 beta
by Peter Bortas ＠ Pike developers forum 21 Jun '09

21 Jun '09

New beta build, 7.8.292: http://pike.ida.liu.se/pub/pike/beta/7.8.304/Pike-v7.8.304.tar.gz Changes since the last beta is a fix for a regression recently introduced in HTTP.Query. Windows build also available today: http://pike.ida.liu.se/pub/pike/beta/7.8.304/Pike-v7.8.304-win32.msi http://pike.ida.liu.se/pub/pike/beta/7.8.304/Pike-v7.8.304-win32.info Untested. Now also has SDL, Freetype and JPEG support, but lost GTK2 support due to a configure conflict. That together with GL support that was already in the last build should mean it's now AIDO capable. But as I said, untested. Do your moderately bad.

3 6

Re: Anyone out there?
by Bill Welliver 15 Jun '09

15 Jun '09

[perhaps pike-devel isn't the best forum for this... should it be moved to the main pike list?] Certainly within each community there are folks with different levels of commitment. To be sure, I know a fair number of Java developers who've drank the "kool-aid" and no amount of coaxing will get them to see that another solution might be better. That said, I think there is a significant minority of Java users who do so just because they have to. They're not sold on it being "the one true way". The reason I suggesed Java users is that syntax and a lot of the philosophy will be familiar so you're not running into what I like to call "the ruby syntax issue". Java developers are also used to things being difficult, even if they're not aware of it, so having to do a little legwork isn't going to be a deal breaker. It's true that most PHP developers I know readily admit that things in PHP land suck a lot of the time. The reason I'm not sure about PHP developers being a good recruiting pool is because, as you point out, they're lazy. The conversation usually goes something like: yeah, that's cool, but who uses it? where are all of the pre-built apps and components i can just configure? people will laugh at me if i don't use something with at least 50% market share. and so on... I do buy the notion that web developers are often willing to try the unproven, after all, they're a big part of why python and ruby are as popular as they are. they know pain, too, in the form of javascript. the question is, what makes things easy? i don't think mod_pike is going to happen, though there's nothing technically preventing it. you'd still run into the problem that until it was ubiquitous, getting it set up and installed is not easy. i mean, getting php set up isn't easy either, if you're doing it yourself. If you weren't afraid of configuring a FastCGI or SCGI app, ScriptRunner gets you the benefits of mod_pike without the horrible security and reliability issues. Perhaps the answer is that someone just needs to package it up (something I don't see myself doing). http://www.gotpike.org/PikeWiki/index.pike/PikeApps/Pike+ScriptRunner http://www.gotpike.org/PikeWiki/index.pike/PikeRequests The Pike wiki at gotpike.org has a wish-list that I think qualify as the "things we need to do to make pike easy" list. Please feel free to add, comment, volunteer. Best, Bill PS. I'm in the US, on the east coast. Not Utah, but at least time zones aren't as bad. I know I'm not the only North American out there, as well. On Sat, 13 Jun 2009, creatorbri(a)gmail.com wrote: > Thanks for the responses thus far. > > You bring up a critical subject: that of the target audience for pike. > I agree that ruby and python devs are a tough crowd. I wonder if Java > devs are any better. There's not much language agnosticism in any of > these groups from what I've seen. At the risk of being discredited > completely by showing an obvious bias, I'd like to suggest an > alternative: Web Developers, and specifically PHP Devs. > > I sense a few eye rolls. I realize the whole Apache discussion is a > mine field so I wanna take a step back. Think instead about what this > bunch is all about. We have to use half a dozen tools to get anything > done, and we're always looking something better because, as much as we > love PHP, we realize that it sucks. The syntax of pike, irrelevant > perhaps to the CS purists, offers a more organized and logical alt. The > biggest hurdle is making it accessible, because we're also some of the > laziest coders you'll find. I'm not saying 'mod_pike'. I'm saying we > just want it simple. > > Finally, keep in mind that although lazy, we are highly adaptive and > tend to latch onto something new quite easily. We're also an exciteable > bunch. If pike ever got an upgrade that put it more readily in the hands > of web devs, I think you'd find your ranks swelling uncontrollably. > > Just my cent-and-a-half. > > Brian > > PS - I am in Utah, USA. Germany is a long walk from my front door. >

1 0

Anyone out there?
by Brian Lacy 13 Jun '09

13 Jun '09

I've just subscribed to the Pike mailing list, and I'm wondering if anyone is still out there in the Pike community. From what I can tell, at least through a rather exhaustive Google search, community support for this sweet little language has all but dried up completely! For historical purposes, necessary or otherwise, the date is June 12, 2009. Thanks, Brian

4 3

README does not document make install or make install_interactive
by Martin Bähr 05 Jun '09

05 Jun '09

hi, for anyone compiling from exported source, is make install_interactive; the recommended way to build and install pike? if so, i guess that should be added to the README? it seems a bit odd to refer users to README-CVS to find out how to install pike after running make. greetings, martin.

3 3

2026

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