Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

Re: Notes from the impromptu developer meetup 2016-07-07
by Chris Angelico 21 Jul '16

21 Jul '16

On Fri, Jul 22, 2016 at 1:05 AM, Martin Bähr <mbaehr(a)realss.com> wrote: > Excerpts from Chris Angelico's message of 2016-07-22 00:46:18 +1000: >> Hah. Actually, I've been pushing more people onto Pike who aren't >> developers, and unfortunately there are a number of trickinesses to >> working on Windows. I've largely come to the conclusion that "Windows >> sucks" is a valid excuse for nearly any bug that I can't repro on >> Linux, but for all those non-developers who want stuff to "just work", >> getting them to install Debian might be a lot of hassle... > > would the linux environment in windows 10 help with that? > pike should work on it, though gtk support won't (unless you get an X > server) so maybe a dealbreaker for you :-( > Lacking GTK would be a killer; so would any additional complexity that lands on the end user, as they're already tending to balk at "install this .msi, then get this .zip and extract it, then double-click gypsum.pike". Also, doesn't help with all the people on Win 7/8. So it's probably going to stay with the native Windows builds for now. That said, though, I don't think the glob changes would break anything I do. ChrisA

1 0

Notes from the impromptu developer meetup 2016-07-07
by Peter Bortas 21 Jul '16

21 Jul '16

We had that impromptu Pike dev meetup on the 7th, and I took notes on some of the things we discussed. Dumping them here before we all forget about it. In attendence: Zino, Nilsson, Grubba, Marcus, Tobi, Arne Status report ------------- Per tradition grubba made a short status report about what has changed since the last meeting: - Some non-enabled new SSL server stuff is not yet compatible with Chrome - We enforce C89 now - GMP is required and always loaded in 8.1 - Threads are allowed while compiling in 8.0 - pragma #dissasemble/#dissassemble (new in 8.1) 8.2 TODO -------- We went though what everyone wants in before we split branch 8.2. In no particular order: - Compiles on Windows For now and until he protests this is zino's problem. - Something about Mpz. Don't remember the details. - Something about lfuns proxy-requested by Per. Don't remember the details. - Add MPI support zinos project. Not really a blocker. - Stop using declarations on the top of the function in C? Debatable - Get the fastcall, fast frames improvements in - glob("C:\*.gif") alt 1: Add Future.glob() depricate glob() import Future alt 2: Consider this a Windows problem and call up the 3 Windows users by phone. alt 3: //Never do this Add heuristics. alt 4: add 8.2::glob dspecial depricate glob constant glob=8.2::glob alt 5: Add String.glob() or similar depricate glob() Maybe reintroduce glob() in a later release We where leaning towards 5. - Stop dumping modules - Move/Remove the Markdown non-module Random notes ------------ - Make a list of all modules and make a note about why each of them are included. Remove the ones with no motivation for them. Nilsson is responsible for the list-making. - Check if anything runs on eureka, otherwise, kill it - Check if we have anything on pelix, otherwise kill it - TravisCI / Coverage - Opera Critic (https://github.com/jensl/critic) Someone said they would have a look att setting that up for Pike last meeting. No one could remember who. - Xenofarm Dates are broken somewhere on the buildmachine which prevents some of the clients from building. - _Roxen module, move the useful stuff somewhere and kill it Make one canonical HTTP module. - Rewrite dirnodes to make them have fewer confusing edge-cases nilsson, grubba - dot-operator is confusing as hell - Use merges to make it easier to track that bugfixes has been merged in which branch Arne will check. - Remove configurability of Calendar Nisson - Make Calendar discoverable for users - Take a look at Image.Orient - Take a look at Image.Graph - Documentation for stuff that inherits ::this_program - Ticket support? (I don't remember what this was about at all) -- Peter Bortas

2 1

Pike 8.0 rel 4 is out
by Peter Bortas 11 Jul '16

11 Jul '16

Pike 8.0 rel 4 is now out. https://pike.lysator.liu.se/pub/pike/latest-stable/Pike-v8.0.276.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/latest-stable/Pike-v8.0.276-Darwin-15.… https://pike.lysator.liu.se/pub/pike/latest-stable/Pike-v8.0.276-win32-oldl… Changes since Pike 8.0.240 (release 3) ---------------------------------------------------------------------- New features ------------ o _Roxen.HeaderParser feed() can now be forced not to normalize (ie lower_case) the header names. o Protocols.WebSocket Added client mode. Bug fixes --------- o Documentation Fixed some AutoDoc markup typos. o Fixed assertion failure in multiset handling. Indexing of non-empty multisets containing no objects or functions, with an object implementing lfun::`<() et al could cause assertion failures. o Filesystem.Monitor Fixed potential recursive mutex locks on destroy(). Regards, -- Peter Bortas

1 0

f_hash() and endianess
by Arne Goedeke 06 Jul '16

06 Jul '16

The documentation of the new f_hash() claims that its return value is architecture independent. SipHash reads its input as a series of little-endian 64 integers, which means that the hash value depends on endianess for wide strings. I have at some point written byte order independent versions of siphash for both 16 and 32 bit strings. Those can be found in commit 21f218e51d55d8c07aff9db0cf45e4ac83050a5e as part of the bloom filter branch. If nobody objects, I will merge that commit into pike 8.1 and integrate it with f_hash(). Something unrelated: I am going to be in linköping from tomorrow until saturday next week. Anyone up for a mini pike meetup? Arne

2 3

String.trim[_all_whites]
by Chris Angelico 06 Jul '16

06 Jul '16

The switch from trim_all_whites to trim broke clean builds on systems where the installed Pike doesn't have trim. The blocker is src/modules/_Charset/make_jisx0213_tables_h.pike, but after fixing that, there are still lots of module precompilation failures, eg: Compiling modules/Gmp/mpz_glue.c /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh precompile.pike '--base=Gmp' "--base=" >"/home/rosuav/pike/src/modules/Gmp/mpq.c" "/home/rosuav/pike/src/modules/Gmp/mpq.cmod" || { rm "/home/rosuav/pike/src/modules/Gmp/mpq.c"; exit 1; } precompile: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/master.pike /home/rosuav/pike/bin/precompile.pike --base=Gmp --base= /home/rosuav/pike/src/modules/Gmp/mpq.cmod (method=Q) /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: 135: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/pike: not found precompile: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/tpike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/master.pike /home/rosuav/pike/bin/precompile.pike --base=Gmp --base= /home/rosuav/pike/src/modules/Gmp/mpq.cmod (method=QQ) /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: 135: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/tpike: not found precompile: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/test-pike /home/rosuav/pike/bin/precompile.pike --base=Gmp --base= /home/rosuav/pike/src/modules/Gmp/mpq.cmod (method=QQQ) /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: 135: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/test-pike: not found precompile: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/master.pike /home/rosuav/pike/bin/precompile.pike --base=Gmp --base= /home/rosuav/pike/src/modules/Gmp/mpq.cmod (method=QQQQQ) /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: 135: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/pike: not found precompile: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/master.pike /home/rosuav/pike/bin/precompile.pike --base=Gmp --base= /home/rosuav/pike/src/modules/Gmp/mpq.cmod (method=QQQQQQ) /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: 135: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/precompile.sh: /home/rosuav/pike/build/linux-4.6.0-1-amd64-x86_64/pike: not found precompile: /usr/local/bin/pike /home/rosuav/pike/bin/precompile.pike --base=Gmp --base= /home/rosuav/pike/src/modules/Gmp/mpq.cmod (method=QQQQQQ) Is this related or separate? The base language interpreter compiles successfully. ChrisA

1 0

Beta/RC 8.0.276
by Peter Bortas 05 Jul '16

05 Jul '16

It the first Tuesday of the month, build day. Last month I never promoted the beta to release because I thought I'd have time for a better Windows build before doing it. Not making that mistake again. Unless this one is bad it's going out as stable. Pike 8.0.276 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.276/Pike-v8.0.276.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.276/Pike-v8.0.276-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.276/Pike-v8.0.276-win32-oldli… Changes since Pike 8.0.240 (release 3) ---------------------------------------------------------------------- New features ------------ o _Roxen.HeaderParser feed() can now be forced not to normalize (ie lower_case) the header names. o Protocols.WebSocket Added client mode. Bug fixes --------- o Documentation Fixed some AutoDoc markup typos. o Fixed assertion failure in multiset handling. Indexing of non-empty multisets containing no objects or functions, with an object implementing lfun::`<() et al could cause assertion failures. o Filesystem.Monitor Fixed potential recursive mutex locks on destroy(). Regards, -- Peter Bortas

1 0

Re: System.Memory and mmap()
by Chris Angelico 14 Jun '16

14 Jun '16

On Tue, Jun 14, 2016 at 6:00 AM, Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > The only other case for SIGSEGV would be to crash your program to > restart it because _Pike itself_ had a bug. I haven't seen that case > for many years. YMMV. GTK2 bugs have been crashing Pike periodically, until they get pinned down and fixed. So Pike bugs _do_ happen, but you can ignore them in mmap. ChrisA

5 4

Re: System.Memory and mmap()
by Mirar ＠ Pike developers forum 13 Jun '16

13 Jun '16

Does Pike have any functionality to catch segfaults and similar errors that might be caused by a bad mmap?

3 6

Revamping the Pike site
by Pontus Östlund 10 Jun '16

10 Jun '16

Hi guys! As awesome a programming language Pike is, the official Pike site does not really reflect that - to say the least ;) The site today does not exacly shout that the language it self is constantly developed and rapidly progressing. I thought I might do something about that. And so I have. Most things are starting to come together, so in a few weeks I feel we can go live with the new site. But before that happens I would love to have your thoughts and feedback on it. At the moment I have the site on my laptop which is not accessible from outsdie, but I’ve put toghether a page with some screenshots and some explainations which you can checkout. I have also revamped the module refdoc to better align with the new site. And since the module refdoc is 100% static HTML pages I’ve put a sample of it online on Github. Page with screenshots and som explainations of the new site: http://poppa.github.io/pike-dumps/ <http://poppa.github.io/pike-dumps/> Module refdoc: http://poppa.github.io/pikedoc/ <http://poppa.github.io/pikedoc/> So feel free to comment and give feedback. Oh, and since there are some really, really, really, really, really, really old content on the site we need to clean up some old stuff that’s no longer viable. I’ve already done some of that on my local copy, but I’ll put together a list of stuff we need to look into. But lets take that later... 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>

8 34

System.Memory and mmap()
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 09 Jun '16

09 Jun '16

I'm looking to interface directly with GPIO-pins on a raspberry pi I just ran into something fishy in pike. It seems that our System.Memory.mmap() method tries to do a ton of checks before it actually calls mmap(). This is all good, until you try to map a device like /dev/gpiomem which is 0 bytes. Should we not attempt the system call and handle the error afterwards instead of trying to emulate safety checks beforehand? Or should we have a new mmap() method that works without the checks?

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