Pike-devel June 2016

pike-devel@lists.lysator.liu.se

6 participants
11 discussions

Optimised map
by Martin Karlgren 09 Jan '17

09 Jan '17

Hi, Having realised the benefits of functional programming, I’ve been quite annoyed by the rumour of how expensive function calls are in Pike. I decided to look into f_map and could see how much seemingly unnecessary work it does when it calls apply_svalue once for each entry in the array – it should be possible to reuse the pike_frame if it’s about to be thrown away after the function call (if it has other refs on the other hand, it can’t be reused – it’s probably used as a scope in some … [View More]

4 12

Promises in Pike vs other languages
by Marcus Agehall (nu med K-m�rkt fastighet och ny elcentral) ＠ Pike (-) developers forum 09 Nov '16

09 Nov '16

I have spent some time looking at the new stuff in Concurrent.pmod that Grubba has added to 8.1. Mostly it is code relating to the concept of Promises and Futures which are very popular amongst JavaScript people these days. I have noted that there seems to be some rather striking differences between how JavaScript treats promises and how Pike does it. I'm not sure this is a good thing(tm) and therefore I'd like to bring this up before 8.1 stabilizes. In Pike, we have two methods that register … [View More]

4 10

Re: Promises in Pike vs other languages
by Per Hedbor () ＠ Pike (-) developers forum 07 Oct '16

07 Oct '16

Something I would recommend, from having written heaps of asynchronous object based systems, with or without remote computers involved, is to treat all references to the promise object going away as an error, and avoid un-needed circular references. This makes it easy to detect when you accidentally forget the object. Also, having the object be callable is rather convenient, it can then be put as a normal callback in all the various function based API:s we already have. >From the MiniRPC … [View More]

4 7

Re: Setting socket options: so many, uhh, options!
by Chris Angelico 15 Sep '16

15 Sep '16

On Tue, Mar 10, 2015 at 10:05 PM, Mirar @ Pike developers forum <10353(a)lyskom.lysator.liu.se> wrote: > Wait, I said REUSEPORT? What's the difference to REUSEADDR? Mysteries > of TCP sockets... Here's a decent explanation, I think: http://stackoverflow.com/questions/14388706/socket-options-so-reuseaddr-and… ChrisA

3 6

Documentation breakage
by Magnus Holmgren, Millnet/Lysator/Debian/Mensa ＠ Pike developers forum 29 Jul '16

29 Jul '16

When preparing a new Debian package of 8.0.240, I noticed that some documentation disappeared, apparently due to the following. The error in Nettle.Sign is already corrected but not the others, AFAICT, and I'm guessing that @exp should be @expr. Patch below, which I home someone can apply right away. ERROR: <Invalid error container: Tools.AutoDoc.AutoDocError(SourcePosition(File: /build/pike8.0-8.0.240/src/modules/Gmp/mpz_glue.c, lines: 668..668), "DocParser", "@exp cannot be used like this:… [View More] @exp{ ... @}")> ERROR: <Invalid error container: Tools.AutoDoc.AutoDocError(SourcePosition(File: /build/pike8.0-8.0.240/lib/modules/__builtin.pmod/Nettle.pmod/Sign.pike, lines: 102..102), "DocParser", "@item is not allowed inside @array (allowed children are: @elem)")> ERROR: <Invalid error container: Tools.AutoDoc.AutoDocError(SourcePosition(File: /build/pike8.0-8.0.240/lib/modules/Crypto.pmod/ECC.pmod, lines: 286..286), "DocParser", "@item is not allowed inside @array (allowed children are: @elem)")> ERROR: <Invalid error container: Tools.AutoDoc.AutoDocError(SourcePosition(File: /build/pike8.0-8.0.240/lib/modules/Crypto.pmod/RSA.pmod, lines: 368..368), "DocParser", "@item is not allowed inside @array (allowed children are: @elem)")> --- a/lib/modules/Crypto.pmod/ECC.pmod +++ b/lib/modules/Crypto.pmod/ECC.pmod @@ -283,9 +283,9 @@ class Curve { //! @returns //! Returns @expr{0@} (zero) on failure, and an array //! @array - //! @item mapping(string(7bit):string(7bit)|int) 0 + //! @elem mapping(string(7bit):string(7bit)|int) 0 //! The JOSE header. - //! @item string(8bit) 1 + //! @elem string(8bit) 1 //! The signed message. //! @endarray //! --- a/lib/modules/Crypto.pmod/RSA.pmod +++ b/lib/modules/Crypto.pmod/RSA.pmod @@ -365,9 +365,9 @@ class State { //! @returns //! Returns @expr{0@} (zero) on failure, and an array //! @array - //! @item mapping(string(7bit):string(7bit)|int) 0 + //! @elem mapping(string(7bit):string(7bit)|int) 0 //! The JOSE header. - //! @item string(8bit) 1 + //! @elem string(8bit) 1 //! The signed message. //! @endarray //! --- a/src/modules/Gmp/mpz_glue.c +++ b/src/modules/Gmp/mpz_glue.c @@ -665,7 +665,7 @@ static void mpzmod_create(INT32 args) /*! @decl int cast_to_int() *! Casts the object to an integer. *! @deprecated - *! Use @exp{(int)@} instead. + *! Use @expr{(int)@} instead. */ static void mpzmod_get_int(INT32 args) { [View Less]

2 2

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 … [View More]

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

Pike 8.0.254 beta/release candidate
by Peter Bortas 08 Jun '16

08 Jun '16

Pike 8.0.254 beta/release candidate: https://pike.lysator.liu.se/pub/pike/beta/8.0.254/Pike-v8.0.254.tar.gz Other builds: https://pike.lysator.liu.se/pub/pike/beta/8.0.254/Pike-v8.0.254-Darwin-15.4… https://pike.lysator.liu.se/pub/pike/beta/8.0.254/Pike-v8.0.254-win32-oldli… SSL certificates where fixed up after last release, so if anyone gets any warnings there let me know. On the positive side I have found my big box of Windows licenses. On the negative side Windows Update … [View More]

1 0

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 June 2016