Pike-devel August 2009

pike-devel@lists.lysator.liu.se

7 participants
25 discussions

More questions about GTK2.SourceView
by Yvan Vander Sanden 24 Aug '09

24 Aug '09

Hi. I am still struggling with SourceView, on windows today. It seems the binary install for windows does not include it. Is there any specific reason for this? Since lots of other libraries are included in the binary, i don't see why gtksourceview is not. Thing is, if i want to make use of gtksourceview in my software, i force my (at the moment fictional) users to compile pike from source, instead of installing a binary. Which makes it much harder to use it. Or is there perhaps another way to use the GTK2.SourceView program, without recompiling pike? Could be I just don't know about it, since i'm only just learning to work with it. Regards, yvan -- Copyright only exists in the imagination of those who do not have any.

2 1

pike language binding for GTK2.SourceView
by Yvan Vander Sanden 23 Aug '09

23 Aug '09

Hello. I was just having a fight with GTK2.SourceView. Seems there was no language binding for pike in it. This being a bit silly, having no syntax highlighting for pike in the pike modules, i tried to find out what was wrong. With help from a few friendly IRC pikers we found this bug report on gtksourceview: http://bugzilla.gnome.org/show_bug.cgi?id=312577 Seems it's not implemented because the mime type for pike is not official. Seems we have to file a request at bugs,freedesktop.org (see comment 6 in link above). Of course i could do that, but it's a bit awkward for me since i'm only using pike for 4 days. It feels a bit too 'official' for me :-) Any other people know more about that? I also corrected a few mistakes in the pike.lang that was attached to the bug report. It's working now and included as an attachement. Regards, yvan -- Copyright only exists in the imagination of those who do not have any.

2 1

share_prefix
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 23 Aug '09

23 Aug '09

There are some occurences of share_prefix in install.pike and master.pike.in, but I understand those are currently only used to let master.pike find the pure Pike modules in lib/modules at build time. However, just a few changes to install.pike are needed to let it actually install those modules in a separate location, in a perhaps more FHS-compliant and Perl-like manner: --- a/bin/install.pike 2009-06-08 23:51:36.000000000 +0200 +++ b/bin/install.pike 2009-08-22 15:46:55.000000000 +0200 @@ -1904,6 +1904,7 @@ string exec_prefix; string lib_prefix; string include_prefix; +string share_prefix; string doc_prefix; string man_prefix; string cflags; @@ -1946,6 +1947,8 @@ lib_prefix=vars->lib_prefix||(prefix+"/lib/pike/"); include_prefix = vars->include_prefix || combine_path(prefix,"include","pike"); + share_prefix = + vars->share_prefix || lib_prefix; doc_prefix = vars->doc_prefix || combine_path(prefix, "doc", "pike"); man_prefix=vars->man_prefix||(prefix+"/share/man/"); @@ -2128,7 +2131,7 @@ lib_prefix = combine_path(prefix, "lib"); include_prefix = combine_path(prefix,"include","pike"); make_master("lib/master.pike", "lib/master.pike.in", - lib_prefix, include_prefix, UNDEFINED, cflags, ldflags); + lib_prefix, include_prefix, share_prefix, cflags, ldflags); status1("Installing master done."); return 0; @@ -2853,10 +2856,10 @@ } else make_master(combine_path(vars->TMP_LIBDIR,"master.pike"), master_src, - lib_prefix, include_prefix, UNDEFINED, cflags, ldflags); + lib_prefix, include_prefix, share_prefix, cflags, ldflags); install_dir(vars->TMP_LIBDIR,lib_prefix,1); - install_dir(vars->LIBDIR_SRC,lib_prefix,1); + install_dir(vars->LIBDIR_SRC,share_prefix,1); install_header_files(vars->SRCDIR,include_prefix); install_header_files(combine_path(vars->SRCDIR,"code"),

1 1

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

Problems with precompile.sh
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 22 Aug '09

22 Aug '09

Patching nettle.cmod uncovered a problem. The tarball ships with the cmods precompiled as C code. But by patching nettle.cmod, nettle.c becomes out-of-date: .cmod.c: $(BUILD_BASE)/precompile.sh-stamp $(TMP_BINDIR)/precompile.pike $(BUILD_BASE)/precompile.sh --cache precompile.pike >"$@" "$<" || { rm "$@"; exit 1; } But precompile.sh tries to run pike like this: if [ x"$1" = xprecompile.pike ] ; then if pike -x 2>&1 | grep precompile > /dev/null 2>&1 ; then shift exec pike -x precompile "$@" fi fi which of course doesn't work if pike isn't already installed.

2 3

Executables without shebang and vice versa
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 22 Aug '09

22 Aug '09

Among the many *.pike (and *.pmod!) files in the module directories there are a few marked as executable but missing a shebang (#!) line, and a few that has a shebang but are not executable. Which ones, if any, are meant to be executed directly? (I'm not talking about scripts that used in the build process, only ones that are installed.) Since none are installed as general-purpose tools in $PATH, and since the ones in Tools.Standalone are meant to be run via pike -x, couldn't you simply delete all the shebangs (which, in case they read "#!/usr/local/bin/pike", are wrong anyway if pike isn't installed under /usr/local) and reset the x bits?

2 3

pike -x httpserver (was: Suggestions for a small menu-driven system?)
by Peter Bortas ＠ Pike developers forum 20 Aug '09

20 Aug '09

This discussion reminded me to check in something I've been having in my tree for a few weeks now; A simple HTTP server available as a standalone (-x) tool. The code is 90% written by Per. I just toolified it. % pike -x httpserver --version Pike httpserver 7.8.337 % pike -x httpserver --help Usage: httpserver [flags] [port] Starts a simple HTTP server on port 8080 unless another port is specified. The server will present the contents of the current directory and it's children to the world without and authentication. --version print version information and exit --help display this help and exit % pike -x httpserver Listening on 8080 The idea is taken from Python, as far as that one of my colleagues asked if Pike can do the equivalent of "python -m SimpleHTTPServer". I haven't actually checked out the python code referenced, so I don't know if -x httpserver is feature equivalent. I find it quite handy for transferring files now and then now that I have it. / Peter Bortas Previous text: >17856137 2009-08-19 22:11 /13 lines/ Brevbäraren >Recipients: Pike (-) importmöte för mailinglistan >Comment to 17855679 >Subject: Re: Suggestions for a small menu-driven system? >-------------------------------------------------------------------- >Martin Nilsson (Opera Mini - AFK!) @ Pike (-) importm?te f?r mailinglistan wrote: >>And that that webserver is good enough to be used for several commercial >>products at Opera. > >Any snippets of sample code you (or anyone else) can share for a minimal >server serving some (e.g. html and gifs) files from the filesystem? >-- >Sincerely, > Stephen R. van den Berg. >Currently unemployed programmer: >"What do you mean, I can't initialize things in an assert()?" > > > >(17856137) /Brevbäraren/-------------------------------------------- >

1 0

[typechecking] Expected int, got int|somethingelse
by Peter Bortas ＠ Pike developers forum 20 Aug '09

20 Aug '09

This program: -------8<-------------------------------------- #pragma strict_types void main() { Stdio.Stat s = file_stat("/etc/passwd"); String.int2size(s->size); } -------8<-------------------------------------- Will cause the following complaint: test-int2size.pike:5: Warning: Type mismatch in argument 1 to int2size. test-int2size.pike:5: Warning: Expected: int. test-int2size.pike:5: Warning: Got : function | string | int. which seems a bit unfair.

2 1

nettle depend in pike ebuild
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 17 Aug '09

17 Aug '09

>hey grubba, > >i am using your pike ebuild via layman. seems like nettle2.0 got the >~x86 keyword removed. as it doesnt work yet with pike, maybe you can put >a <=dev-libs/nettle-1.15 into the ebuild dependencies. It should already be there: | $ grep nettle /usr/local/portage/layman/pike/dev-lang/pike/pike-7.8.316.ebuild | DEPEND="<dev-libs/nettle-2 Try running layman -S >best > >arne

2 1

pike -x cflags, include_prefix
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 14 Aug '09

14 Aug '09

Tools.Standalone.cflags prints master()->cflags, which typically equals "-DDYNAMIC_MODULE -I" + dirname(master()->include_prefix). Tools.Standalone.module uses master()->include_prefix directly, however. Explanation? When is Tools.Standalone.cflags meant to be used? "New style" modules? Are sources relying on master()->cflags to be compiled meant to #include <pike/whatever> instead of #include <whatever>?

2 2

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