Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Constants with program with parent dependency
by Arne Goedeke 27 Jun '17

27 Jun '17

Hi all, the following code does not work anymore in pike 8: constant fail = ({ A }); class A { array foo = fail; } As far as I can tell the reason was that previously unfinished programs were not considered to use their parent and so the reference of A in the array ended up being a program instead of the function. The commit which introduced this change in behavior was 86ce26dde736531829bbf1466c0d2504e8973466 My feeling is that the new behavior is actually correct, or is this a regression? Arne

1 0

Major problem with SQLite binding handling
by H. William Welliver III 21 Jun '17

21 Jun '17

I’ve noticed an odd problem a few years ago with using parameter bindings with SQLite and never really took the time to figure out the cause until now. I think it’ a pretty major problem that can be easily fixed, though would cause problems for anyone relying on the (imo) currently broken behavior. Basically, the problem is that when using parameter bindings with strings, the pike glue determines the type of the data based on the width of the string: if it’s a wide string, the parameter is bound as a text, but if it’s 8 bit, it’s bound as a blob. The problem is that text and blob values aren’t evaluated the same, so even though a text value and blob value may be identical byte-wise, they are not equal when doing comparisons and so queries that would seem to match actually don’t. This is compounded by the fact that SQLite has no restrictions on what may be stored in a field (type definitions on a table are merely default suggestions) and SQLite will happily store whatever you want (such as a blob value in a text field). For example, imagine a table m with an integer field id and a char field value: s->query(“INSERT INTO m VALUES(1, 'value a’)); s->query(“INSERT INTO m VALUES(2, :value)”, ([“:value”, “value a”])); s->query(“SELECT * FROM m where value=‘value a’”); The third query will return 1 record instead of the expected 2 because the field value in the second row is stored as a blob and thus does not match a text query. In order to retrieve both records, you must use LIKE or know to cast the value to text using “AS TEXT” in the query, which is obviously a lot less ideal in most cases. If all of your data is stored using the pike glue, and you’re always using parameters, it’s possible never to see the problem, but if not, this causes all kinds of problems because of the need for constantly casting values and possibly using blob literals, which are not human readable when you’re really trying to query for a non-wide string. My suggestion is to change the binding type for 8 bit string parameters to text in order to match the rest of the string handling. It would be good to have a datatype that caused a parameter to be bound as a blob, either a native byte array or some object that wraps an 8 bit string (Sql.BinaryString?) in order to cause the binding to act accordingly. Of course, this causes a compatibility problem for anyone who was using pike binding with bindings previously (is there anyone who us doing this and hasn’t run into this problem?), as any 8-bit strings that weren’t binary data would be stored as blobs, even if they were in a text typed field. These records would need to be re-stored with the proper text type, which could be done with a query to update the table. My sense is that this is the proper thing to do, as blob fields should be reserved for data that’s actually binary data (as opposed to text). Thoughts?

3 3

Pike 8.0.450 beta
by Peter Bortas 18 Jun '17

18 Jun '17

Onl popular demand, Pike 8.0.450 beta: https://pike.lysator.liu.se/pub/pike/beta/8.0.450/Pike-v8.0.450.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.450/Pike-v8.0.450-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.450/Pike-v8.0.450-win32-oldli… This is not a release candidate, just something that includes Concurrent to play with until there is a real release. Changes since Pike 8.0.438 (release 9) ---------------------------------------------------------------------- New Features ------------ o Concurrent The Concurrent module simplify asynchronous code by synchronizing events in different ways. As an example the connection() function shown will repond with Concurrent.Promise object that at some point will represent either a connected socket or a failure. Concurrent.Promise connection(string host, int port) { Stdio.File con = Stdio.File(); Concurrent.Promise p = Concurrent.Promise(); if( !con->async_connect(host, port, lambda(int success) { if(success) p->success(con); else p->failure("Failed to connect to "+host+":"+port+"\n"); })) { p->failure("Failed to open socket.\n"); } return p; } The returned promise could the be used in various ways. // On success, call make_request(con, query). On failure call // werror(msg). connection(host, port) ->on_failure(werror) ->on_success(make_request, query); // On success, call make_request(con, query1) followed by // make_request(resp, query2), where resp is the return value from // make_reqest. connection(host, port) ->then(make_request, werror, query1) ->then(make_request, werror, query2); // Call bridge_ports(con1, con2) when both connections are // established. Concurrent.all(connection(host1, port1), connection(host2, port2)) ->then(bridge_ports, failure); // Call make_request(con) once either of the connections are // established. Concurrent.race(connection(host1, port1), connection(host2, port2)) ->then(make_requet, query); Bug fixes --------- o Search Fixed a race condition when updating the database. o Parser.HTML Fixed a condition where Pike would run out of stack space for large documents. o ADT.Heap Fixed heap corruption when the same object is pushed more than once. It will now be considered as calling adjust(). o Inotify - Addressed an issue where the backend might be stuck in pending indefinitely. - EventStreamMonitor now works with other backends. o Standards.BSON Fixed incorrect encoding/decoding of Binary data. o Stdio.Buffer Fixed a crash when attempting to create a rewind key on a buffer returned by read_buffer(). o mappings Fixed an off by one error in random(mapping) that randomly caused values of type PIKE_T_FREE from the freelist to be exposed to Pike.

1 0

Pike 8.0 release 9 RC1
by Peter Bortas 11 Jun '17

11 Jun '17

Pike 8.0.438 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.438/Pike-v8.0.438.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.438/Pike-v8.0.438-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.438/Pike-v8.0.438-win32-oldli… Changes since Pike 8.0.404 (release 8) ---------------------------------------------------------------------- New Features ------------ o Calendar Updated Calendar to use timezonedata from tzdata2017a. o GL & GLUT Prefer Quartz implementation on systems that have it (OS X). o GTK2 - Add -x objective-c for Darwin. - Support linking against other implementations than X11. o Protocols.HTTP Connecting to HTTP proxies over HTTPS is now supported. o Web.decode_jwk() Support decoding of symmetric (ie HMAC) keys. o Web.encode_jws() and Web.decode_jws() Added simplified API for dealing with JSON Web Signature values. Bug fixes --------- o Runtime - Variant dispatcher Improved string range checking. Fixes mismatches due to te lazy string range (ed string(8bit)) exceeding the typed string range (eg string(7bit)) for narrow strings. o mkpackage Support multiple sub-packages with the same name. Gnu-tar doesn't like being asked to extract the same file multiple times from the same tar-file. It claims that the second file doesn't exist in the archive. This can happen when a sub-package has been replaced with a fixed version. o smartlink Don't override MACOS_DEPLOYMENT_TARGET if it's been specified. This should prevent "compiled against version x but linking against version y" warnings. o Arg & ADT.Struct Survive use by old (ie 8.0.232) pike binaries. Roxen 6.0.130 uses a Pike 8.0.232 binary with current modules. o Backend.PollDeviceBackend Make set_signal_event_callback() optional. This fixes the warning "An expression of type function({ Backend = object(implements _static_modules.Builtin()->defaultBackendClass) } : void) cannot be assigned to a variable of type function({ Backend = object(implements _static_modules.Builtin()->Backend) } : void).". o bool Make sure that 0 is part of the range for the bool type. o Charset Fixed encoding errors for two characters in the GSM-03.38 charset. o Debug Fixed typo in mask in check_callback_chain(). Fixes infinite loop in circularity detection. o Gdbm Support building with gdbc 1.13. Fixes obscure compilation error when building with gdbm 1.13 due to a symbol clash with the symbol "fatal" used as an argument in the macro definition of gdbm_set_errno(). o Mapping Removed extraneous and conflicting prototype. Fixes linking issues on NT. o Protocols.HTTP - Fixed do_async_proxied_method() losing the timeout during TLS negotiation. - Now fails immediately if Query is unable to open a socket, instead of waiting 120 seconds for a time out. - Allow connection reuse also when the server is a hostname. o Thread.Mutex - Perform a thread yield on mutex onlock in an attempt to reduce thread starvation. o Sql.pgsql - Added an extra synchronisation condition, and increased parallelisation to resolve all detected race conditions (which in rare circumstances (many parallel queries on a single filedescriptor) could have resulted in a deadlock). -- Peter Bortas

1 0

Time for a release
by Peter Bortas 05 Jun '17

05 Jun '17

It's the first Tuesday in the month, and thus release time. The last couple of months the changes in stable did not motivate fixing missing CHANGES myself and pushing a release. And there are some checkins without changes, which violates stable policy. So review your stuff and check in CHANGES. -- Peter Bortas

1 0

Protocols.HTTP.Query dns cache
by H. William Welliver III 02 Jun '17

02 Jun '17

I was troubleshooting a problem earlier today and noticed that: a) Synchronous calls in Protocols.HTTP.Query don’t populate the DNS cache and b) The doesn’t seem to be any TTL for entries in either the cache Query or the one in Session. I didn’t remedy a) because I think doing so without having a way to expire records would cause undesirable behavior for hostnames (especially) with multiple addresses. Any cache probably ought to at least respect the TTL on the DNS record as an upper bound. Does anyone have any thoughts about this? Bill

2 1

GDK/GTK on OSX
by H. William Welliver III 29 May '17

29 May '17

Note: I actually sent this email to Chris a month ago but it didn’t go to the list, so I’m sending it there so that there’s a record of this conversation. Hi Chris, I’ve been quietly working on this for a few weeks now, and have got the various permutations working on OS X. Basically, there are 2 paths for GTK on OS X (now called macOS): X11, which is the classic approach, and Quartz, which is native, but newer and a little less fully baked. Homebrew, a very popular package manager on OS X, switched to Quartz mode at some point, which broke the pike builds. This sort of dual mode situation affected GL and GLUT as well. So, I’ve arrived at a solution where we prefer the native Quartz versions but will fall back if they’re not present (such as if you happen to be running the Darwin open source OS that macOS is based on. I think that’s the most reasonable approach because every macOS install will have Quartz, GL and GLUT (and using GTK doesn’t require you to install X11/XQuartz. I’ve merged your change into 8.1 and 8.0 after testing, along with a bunch of other fixes to get things working. I have not been able to verify that the changes work properly on Windows because I am having trouble getting the windows build to compile successfully. Likely because I foolishly tried to upgrade to VC2015 from VS2008, which was working properly. There are also a number of problems with other bits of the 8.1 codebase that cause problems on Windows, though I see some commits lately that seem to suggest that may be a temporary thing. Anyway, that’s the current update. And to answer your question about being able to run gtk apps on macOS without having to install X11, here’s a little taste : object x; int main() { GTK2.setup_gtk(); x = GTK2Support.Alert("Hello world!"); return -1; } Yields: http://bill.welliver.org/dist/pike/gtkmacdialog.png <http://bill.welliver.org/dist/pike/gtkmacdialog.png> Enjoy! Bill

2 2

Bad function identifier on 8.1
by Stephen R. van den Berg 29 May '17

29 May '17

While trying to use Pike 8.1, I consistently get the following on stderr whenever I run pike: /usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod.o:-: Warning: Decode failed: Error while decoding program(/usr/local/pike/8.1.6/lib/modules/Crypto.pmod/Random.pmod:23): Bad function identifier offset for random_string:function(int(0..2147483647) : string(8bit)): 3 != 0 It's not immediately obvious to me how to fix this. Anyone? Or am I the only one seeing this? -- Stephen.

2 4

pike compile failes on fedora 25 x86_64
by josef radinger 22 May '17

22 May '17

hi i try to compile pike for fedora 25 and it fails as below: ... precompile: /usr/local/bin/pike80 /tmp/Pike- v8.0.404/bin/precompile.pike --base=FSEvents /tmp/Pike- v8.0.404/src/modules/FSEvents/fsevents.cmod (method=QQQQQQ) Compiling modules/FSEvents/fsevents.c Linking FSEvents #### Making dynamic: modules/Fuse Compiling modules/Fuse/fuse.c Linking Fuse Making module.pmod #### Making dynamic: modules/Gdbm Compiling modules/Gdbm/gdbmmod.c /tmp/Pike-v8.0.404/src/pike_error.h:54:34: error: expected ‘)’ before string constant (fprintf(stderr,msg_fatal_error,__FILE__,(long)__LINE__),debug_fatal) ^ In file included from /tmp/Pike-v8.0.404/src/threads.h:11:0, from /tmp/Pike-v8.0.404/src/modules/Gdbm/gdbmmod.c:9: /tmp/Pike-v8.0.404/src/pike_error.h:54:58: error: expected ‘)’ before ‘,’ token (fprintf(stderr,msg_fatal_error,__FILE__,(long)__LINE__),debug_fatal) ^ Compilation command was: /tmp/Pike-v8.0.404/build/linux-4.10.8-200.fc25.x86_64-x86_64/smartlink gcc -I. -I/tmp/Pike-v8.0.404/src/modules/Gdbm -I/tmp/Pike- v8.0.404/build/linux-4.10.8-200.fc25.x86_64-x86_64 -I/tmp/Pike- v8.0.404/src -I/usr/local/include -DHAVE_CONFIG_H -g -ggdb -m64 - mrdrnd -fvisibility=hidden -O3 -pipe -fvar-tracking-assignments -funswitch-loops -W -Wall -Wno-unused -Wcomment -Wformat -Wimplicit- function-declaration -Wmultichar -Wunused-function -Wswitch -Wuninitialized -Wpointer-arith -Wchar-subscripts -Wno-long-long -Wdeclaration-after-statement -fPIC -DDYNAMIC_MODULE -c /tmp/Pike- v8.0.404/src/modules/Gdbm/gdbmmod.c -o gdbmmod.o Makefile:167: recipe for target 'gdbmmod.o' failed make[6]: *** [gdbmmod.o] Error 1 Makefile:100: recipe for target 'all' failed make[5]: *** [all] Error 2 Makefile:100: recipe for target 'Gdbm' failed make[4]: *** [Gdbm] Error 1 Makefile:1175: recipe for target 'dynamic_module_objects' failed make[3]: *** [dynamic_module_objects] Error 1 Makefile:1195: recipe for target 'module_objects' failed make[2]: *** [module_objects] Error 2 Makefile:149: recipe for target '_make_in_builddir' failed make[1]: *** [_make_in_builddir] Error 2 Makefile:66: recipe for target 'compile' failed make: *** [compile] Error 2

2 3

Faster calls (again)
by Arne Goedeke 20 Mar '17

20 Mar '17

Ok, not sure yet if this is going anywhere this time, but I decided to attempt a second time to refactor the current function call code into something which is more readable, more flexible and hopefully faster (at some point). The branch is called 'arne/faster_calls_again'. The API is similar to what the previous version did, the main difference being that it allocates pike frames only if needed (not for efuns, casts, apply_array, etc). The changes in that branch start by first removing code which was duplicated at some point to increase performance for certain types of calls. I then added a series of new functions to initialize, execute and deinitialize a callsite. Then, I started to use it in some of the existing function call APIs and also implemented that optimized version of f_map. The code is probably broken in interesting ways, I have not tested it very well, yet. It compiles and installs. Otherwise on my list right now: * cleanup * reduce API granularity somewhat * re-add tracing and dtrace code (could all be in one place now) * optimize automap * try to optimize apply_array (e.g. when calling the same function in different instances of the same class) * make tail recursion not allocate a new frame, instead just re-use the current one Feedback and help welcome, Arne

3 8

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