Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Re: glob() in 8.1
by Peter Bortas ＠ Pike developers forum 16 May '16

16 May '16

For the record: I will push for 8.2 at the latest Q1 next year. Going for a 9.0 in Q2 instead would be manageble I think. I'm somewhat worried that it was easy to construct a plausible test case where the the glob behaviour will break old code: Pike v7.8 release 834 running Hilfe v3.5 (Incremental Pike Frontend) > array files = ({ "C:\\foo.bat", "C:\\bar.exe" }); > glob("C:\\*.exe", files); (2) Result: ({ /* 1 element */ "C:\\bar.exe" }) Pike v8.1 release 4 running Hilfe v3.5 (Incremental Pike Frontend) > array files = ({ "C:\\foo.bat", "C:\\bar.exe" }); > glob("C:\\*.exe", files); (1) Result: ({ }) Handling this with deprication isn't possible in a nice way, but I do think it's a change we want to make. How about this butt ugly gludge: Make a pike-global flag switching to the new behaviour. Depricate-warn for any use of glob in 8.2 that isn't first setting that flag or using the compatibility interface to directly specify a version. The flag could be full-hog ugly: Make it a command line switch. Or something you set in the master. Or a new builtin. :-/ I guess I'm talking about "import from Future". Ugh.

1 0

Re: New stable release: 8.0.240
by Peter Bortas 15 May '16

15 May '16

On Sun, May 15, 2016 at 4:18 PM, Peter Bortas <bortas(a)gmail.com> wrote: > polishing and a recommended upgrade. New for this release is a MacOSX > binary build. Please note that the Mac build is a executable installer > that requires gmp and nettle from macports to run though. I haven't built a MacOS release since leaving Roxen many years ago, but I brought out a Mac Mini from storage and set it up this weekend. If someone tells me how to build a .pkg I'll try to do that for the next release. I assume it has something to do with packaging/macosx/framework_Info.plist? That file has been rotting since 7.7 though, so input from developers on MacOSX would be valuable here. -- Peter Bortas

1 0

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

13 May '16

Granted more manageble for code I maintain myself, but it doesn't eliminate the problem in theory. I think it ultimately depends on what 8.1 is intended to be when it is released: a drop-in upgrade in 8.0 environments, or a major step like 7.x to 8.0? If it will become Pike 9.0 and introduce a bunch of other incompatibilities I'd be more open to that change, but not otherwise.

1 0

Re: glob() in 8.1
by Per Hedbor 13 May '16

13 May '16

Well. Is [ and \ really that common in glob patterns? (the addition of quoting and making [ a control character being the incompatible changes) It is possible to use 8.0::glob (not yet in place). Or this, which is future compatible (8.0:: would be removed after a while): add_constant( "glob", lambda(array|string a, array|string b) { array(string)|string compat(array|string what) { if(arrayp(what)) return map(what,this_function); return replace(what, (["\\":"\\\\", "[":"\\[" ])); }; return !!glob(compat(a),b); }); (since I don't think any of the array version are used in roxen, it can be simplified a bit.. :)) Anyway, the glob function in 8.1 complies with the definition of glob in wikipedia, whatever that is worth. As for why glob was modified: The lack of quoting made it impossible to match * or ?. The [ is less important to me at least, I just added that to be feature complete (or, well, to the 'basic' glob pattern syntax). After perusing the roxen source there are very few locations where the pattern is not a simple constant *.<ext>, only a few places takes the pattern as input from the user (web developer). In most cases this seems to then be matched to a mime type ([ and \ being somewhat uncommon in those) or a file (not path) name (no \, theoretically [ can occur), Of course, custom code can do whatever. On Fri, May 13, 2016 at 4:10 PM, Jonas Walldén @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > 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.

2 2

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 06 May '16

06 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

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