Pike-devel

pike-devel@lists.lysator.liu.se

2 participants
3046 discussions

glob() in 8.1
by Jonas Walld�n ＠ Pike developers forum 13 May '16

13 May '16

Just saw Per's checkin (781fcde2) in 8.1: > Extended glob pattern syntax: > o \ can now be used to quote special characters in the pattern > o [ can be used for ranges of characters ([bx] [a-c0-9] [^a] etc). > > Also changed glob to return the matching glob instead of 1 when an > array is passed as the first (pattern) argument. > > This can be used to remove some loops where you want to do > different things depending on which pattern matched. > > Both these changes are incompatible. Can we please put this in a new method or use opt-in with an extra flag? I'm not too worried about the return value, but the changes in glob parsing sound problematic to me. At least for our customers there are plenty of globs in user data (RXML code, system configs, custom modules etc) that could misbehave silently, i.e. without producing compile-time errors.

1 0

Pike 8.0.240 release candidate
by Peter Bortas 09 May '16

09 May '16

I did an effort to get a Windows 10 environment up this weekend, but it's not done. So here is a release candidate together with an old classically compiled Windows version. If no one finds anything bad (where bad is worse than the latest stable) this will be the release next weekend. Pike 8.0.240 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.240/Pike-v8.0.240.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.240/Pike-v8.0.240-win32-oldli… -- Peter Bortas

3 2

Promises and HTTP
by Pontus Östlund 06 May '16

06 May '16

Hi guys! I started experimenting with the new Concurrent.Promise/Concurrent.Future classes and implementing a HTTP client module using the promise/future stuff. The reason for this is that the async stuff in Protocols.HTTP.Query is far from intuitive. With promises/futures I think you get a super clean API that is easy to use. So I started experimenting with this and would like to have your thoughts on the matter. Right now I put it as Protocols.HTTP.Promise but any suggestions on what to call it and where to place it would be appreciated. Here’s some examples of how it would be used at the moment. // Fetch a single URL import Protocols.HTTP; int main() { string url1 = ”http://pike.lysator.liu.se <http://pike.lysator.liu.se/>”; Concurrent.Future q1 = Promise.get_url(url1); q1->on_success(lambda (Protocols.HTTP.Query ok) { werror(”Successfully got %O\n”, ok->host); })->on_failure(lambda (Protocols.HTTP.Query fail) { werror(”%O failed!\n”, fail->host); }); return -1; } // Fetch multiple URLs and call on_success in parallell for each request. import Protocols.HTTP; int main() { string url1 = ”http://pike.lysator.liu.se <http://pike.lysator.liu.se/>”; string url2 = ”http://roxen.com <http://roxen.com/>”; Concurrent.Future q1 = Promise.get_url(url1); Concurrent.Future q2 = Promise.get_url(url2); array(Concurrent.Future) all = ({ q1, q2 }); all->on_success(lambda (Protocols.HTTP.Query ok) { werror(”Successfully got %O\n”, ok->host); })->on_failure(lambda (Protocols.HTTP.Query fail) { werror(”%O failed!\n”, fail->host); }); return -1; } // Fetch multiple URLs and call on_success when all has succeeded. // on_failure will be called immediately if one request fails. import Protocols.HTTP; int main() { string url1 = ”http://pike.lysator.liu.se <http://pike.lysator.liu.se/>”; string url2 = ”http://roxen.com <http://roxen.com/>”; Concurrent.Future q1 = Promise.get_url(url1); Concurrent.Future q2 = Promise.get_url(url2); Concurrent.Future batch = Concurrent.results(({ q1, q2 })); all->on_success(lambda (array(Protocols.HTTP.Query) ok) { werror(”Successfully got %O\n”, ok->host); })->on_failure(lambda (Protocols.HTTP.Query fail) { werror(”%O failed!\n”, fail->host); }); return -1; } So, any thoughts on this? Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

2 4

CHANGES for next release
by Peter Bortas ＠ Pike developers forum 05 May '16

05 May '16

Should any of the following have a CHANGES note?: * ADT.Heap: Added low_peek(). * Fix GTK2.SourceBuffer undo/redo signal names * Fix spelling of composite[d]_changed signal - Is that an API change or where the signals not properly hooked up before? * Crypto/SSL - There is a ton of Crypto/SSL changes. I'm just going to trust Nilsson and/or Grubba to make sure relevant things are in CHANGES.

3 2

Problems building Pike on Mac
by Pontus Östlund 03 May '16

03 May '16

I recetly started getting this build error, which I have absoluteley no clue what to do about: […] In file included from /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:16: /Users/ponost/src/pike-git/devel/src/module_support.h:47:1: warning: target does not support 'protected' visibility; using 'default' [-Wunsupported-visibility] PMOD_EXPORT void get_all_args(const char *fname, INT32 args, ^ /Users/ponost/src/pike-git/devel/src/global.h:624:42: note: expanded from macro 'PMOD_EXPORT' # define PMOD_EXPORT __attribute__ ((visibility("protected"))) ^ In file included from /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:16: /Users/ponost/src/pike-git/devel/src/module_support.h:49:1: warning: target does not support 'protected' visibility; using 'default' [-Wunsupported-visibility] PMOD_EXPORT void pike_module_export_symbol(const char *str, ^ […] /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:426:19: error: use of undeclared identifier 'f_Nettle_Cipher_name_fun_num' apply_external(1, f_Nettle_Cipher_name_fun_num, args); ^ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:452:19: error: use of undeclared identifier 'f_Nettle_Cipher_block_size_fun_num' apply_external(1, f_Nettle_Cipher_block_size_fun_num, args); ^ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:466:37: error: use of undeclared identifier 'Nettle_Cipher_program'; did you mean 'nettle_hash_program'? struct Nettle_Cipher_struct *info = GET_INFO(); ^ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:288:70: note: expanded from macro 'GET_INFO' #define GET_INFO() ((struct Nettle_Cipher_struct *)parent_storage(1, Nettle_Cipher_program)) ^ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/nettle.h:24:24: note: 'nettle_hash_program' declared here extern struct program *nettle_hash_program; ^ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:469:26: error: incomplete definition of type 'struct Nettle_Cipher_struct' memset(THIS->ctx, 0, info->meta->context_size); ~~~~^ /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/include/secure/_string.h:77:38: note: expanded from macro 'memset' __builtin___memset_chk (dest, val, len, __darwin_obsz0 (dest)) ^~~ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:466:8: note: forward declaration of 'struct Nettle_Cipher_struct' struct Nettle_Cipher_struct *info = GET_INFO(); ^ /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.cmod:544:19: error: use of undeclared identifier 'f_Nettle_Cipher_name_fun_num' apply_external(1, f_Nettle_Cipher_name_fun_num, args); ^ fatal error: too many errors emitted, stopping now [-ferror-limit=] 518 warnings and 20 errors generated. Compilation command was: /Users/ponost/src/pike-git/devel/build/darwin-15.4.0-x86_64/smartlink gcc -I. -I/Users/ponost/src/pike-git/devel/src/post_modules/Nettle -I/Users/ponost/src/pike-git/devel/build/darwin-15.4.0-x86_64 -I/Users/ponost/src/pike-git/devel/src -Dpike_module_init=pike_module_Nettle_init -Dpike_module_exit=pike_module_Nettle_exit -I/usr/local/include -I/usr/X11/include -I/usr/X11R6/include -DHAVE_CONFIG_H -g -std=c99 -ggdb -m64 -mtune=750 -mrdrnd -fvisibility=hidden -O3 -pipe -W -Wall -Wno-unused -Wcomment -Wformat -Wformat-security -Wimplicit-function-declaration -Wmultichar -Wunused-function -Wswitch -Wuninitialized -Wpointer-arith -Wchar-subscripts -Wno-long-long -c /Users/ponost/src/pike-git/devel/src/post_modules/Nettle/cipher.c -o cipher.o make[5]: *** [cipher.o] Error 1 make[4]: *** [all] Error 2 make[3]: *** [Nettle] Error 1 make[2]: *** [post-modules-stamp] Error 1 make[1]: *** [_make_in_builddir] Error 2 make: *** [compile] Error 2 I guess this is Grubba’s area? ;) Regards ----------------------------- Pontus Östlund Developer • Roxen AB +46 70-662 81 69 www.roxen.com <http://www.roxen.com/> | twitter.com/roxen <https://twitter.com/roxen>

2 2

Wrong enum type
by Arne Goedeke 03 May '16

03 May '16

An enum with two elements can get the wrong resulting type: > enum A { a, b }; Compiler Warning: 2: a is private but not used anywhere. Compiler Warning: 2: b is private but not used anywhere. Compiler Warning: 2: A is private but not used anywhere. (1) Result: int(1..1) The problem seems to be in or_pike_types handling of T_ZERO, but I am unsure about how that should be fixed. Also, whats the point of those warnings about private unused definitions? Is that a hilfe issue? Arne

1 0

This weeks stable attempt.
by Peter Bortas 02 May '16

02 May '16

Tomorrow is the first Tuesday of the month, so I will as usual attempt to make a stable release. This week there is however a four day weekend, which chance to have a look at some larger changes on the Windows side. The actual release will if it happens be on Sunday the 8th. Regards, -- Peter Bortas

1 0

Re: Stdio.File()->pipe() and PROP_IPC
by Chris Angelico 27 Apr '16

27 Apr '16

On Thu, Apr 28, 2016 at 1:40 AM, Henrik Grubbström (Lysator) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: >>Consider this usage: >> >>object stdout = Stdio.File(); >>Process.create_process(cmd, (["stdout": stdout->pipe()]); >> >>Is this at risk of failing, where stdout->pipe(Stdio.PROP_IPC) would succeed? > > Not currently, as the default type of pipe generated by pipe() is > fd_pipe() (which maps to CreatePipe on WIN32 and is IPC capable). > >>Does that imply that PROP_IPC is effectively always implied when >>creating a pipe? > > Not on WIN32. All currently-supported platforms appear to have IPC capabilities in the default pipe. Would it be worth changing the default from PROP_NONBLOCK|PROP_BIDIRECTIONAL to PROP_NONBLOCK|PROP_BIDIRECTIONAL|PROP_IPC? That wouldn't break any current code, and would mean that simple calls to stdout->pipe() would be guaranteed to work (instead of just happening to work). ChrisA

2 1

Stdio.File()->pipe() and PROP_IPC
by Chris Angelico 27 Apr '16

27 Apr '16

What exactly does PROP_IPC (fd_INTERPROCESSABLE in the source) permit? Consider this usage: object stdout = Stdio.File(); Process.create_process(cmd, (["stdout": stdout->pipe()]); Is this at risk of failing, where stdout->pipe(Stdio.PROP_IPC) would succeed? I can't find anything that indicates exactly what "IPC" means, and whether using one end of a pipe for a process's standard stream counts as IPC. It seems like it ought to, but the Pike standard library isn't consistent about requesting it (see Sql.pmod/rsql.pike:36, Git.pmod/Export.pike:46, and githelper.pike:60 from the companion repo). In _Stdio/file.c, file_pipe(), checks are made for a pipe (if PIPE_CAPABILITIES is defined), a socketpair, or a socketpair_ultra. All three of these have fd_INTERPROCESSABLE set, so far as I can tell. Does that imply that PROP_IPC is effectively always implied when creating a pipe? ChrisA

2 1

Re: Pike 8.0.222 release candidate
by Chris Angelico 24 Apr '16

24 Apr '16

On Wed, Apr 6, 2016 at 10:25 AM, Peter Bortas @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Well, the build machine is an XP. I don't mind dropping anything > before 7. But that means a whole new build environment. Not happening > this week. Fair enough. I'd guess that GTK 2.24.30 should run on XP, at least. I'm just picking this up again after a flat-out week of musical theatre, and am finding this: http://gtk-win.sourceforge.net/home/index.php/Main/Downloads The other option would be compiling GTK itself from source: http://ftp.gnome.org/pub/gnome/sources/gtk+/2.24/ ISTR the last time I tried to build Pike on Windows was a bit of a disaster. Sadly, there is nothing simple about cross-compilation. It'd be really awesome if the Windows 10 Linux subsystem makes that easier. ChrisA

2 3

Jump to page:

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