Pike-devel March 2015

pike-devel@lists.lysator.liu.se

8 participants
13 discussions

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

config error
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 31 Mar '15

31 Mar '15

I feel like I've run into this before. Any better way of solving it than a cleaning the source tree? ./config.status --recheck running CONFIG_SHELL=/bin/bash -norc /bin/bash -norc /home/nilsson/pike/src/configure --no-create --no-recursion ./config.status: line 530: /bin/bash -norc: No such file or directory ./config.status: line 530: exec: /bin/bash -norc: cannot execute: No such file or directory make[2]: *** [config.status] Error 126 make[1]: *** [_make_in_builddir] Error 2 make: *** [compile] Error 2

2 1

autoconfig autoheader not found
by robert papadopoulos 29 Mar '15

29 Mar '15

In attempting to build Pike 8.0 I was met with a slew of errors. I used the make command as specified. the errors begin... cd src && ./run_autoconfig . ./run_autoconfig: 1: ./run_autoconfig: autoconf: not found ./run_autoconfig: 70: [: Illegal number: Warning: Using autoconf < 2.50. Don't do this if you want to make export. followed by a hundred or so lines of ./run_autoconfig: 139: ./run_autoconfig: autoheader: not found ./run_autoconfig: 143: ./run_autoconfig: Running autoconf in . with variations on the path. I was successfully able to build Pike 7.8 and play around with it using the same method. Can any body provide any advice to get me up and running? I'm running Linux Mint 17 Qiana 32 bit XFCE.

2 2

errors in makecheck pike 8.0
by robert papadopoulos 29 Mar '15

29 Mar '15

So, I had to do a little research on autoconf, but I'm back for more. I used version 2.58 and recieved the following errors/skippages. I'm assuming a lack of fortran is the reason for the skipped gimmicks, but I am stumped by the rest. Mr Welliver, thank you for your help in the last email for getting me one step further than I previously was. ## ------------- ## ## Test results. ## (from make check)... ## ------------- ## ERROR: 172 tests were run, 4 failed unexpectedly. Executables (autoheader, autoupdate...). 3: autom4te cache FAILED (tools.at:131) 4: autoconf --trace: user macros FAILED (tools.at:180) M4sugar. 13: [m4_warn] FAILED (m4sugar.at:59) 14: [m4_require: circular dependencies] FAILED (m4sugar.at:107) 40: Configuring subdirectories skipped (torture.at:562) 41: Deep Package skipped (torture.at:658) 66: GNU Fortran 77 skipped (fortran.at:33) 67: GNU Fortran skipped (fortran.at:61) Testing autoconf/fortran macros. 68: AC_F77_MAIN skipped (acfortran.at:12) 69: AC_F77_WRAPPERS skipped (acfortran.at:13) 70: AC_FC_MAIN skipped (acfortran.at:14) 71: AC_FC_WRAPPERS skipped (acfortran.at:15) 72: AC_PROG_F77_C_O skipped (acfortran.at:16) 73: AC_PROG_FC_C_O skipped (acfortran.at:17) Also, autoconf documentation tells me that it should be installing pike to my bin, but it has yet to make it there. I can of course run pike from its home directory...but where's the fun in that? Hope this email finds all who receive it well. Linux Mint XFCE 32 bit OS

2 1

8.0
by Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum 21 Mar '15

21 Mar '15

> Would anyone object to releasing 8.0 from 8.0.38? Sounds good to me. I don't think I have any known major issues left to fix.

3 10

8.0 release
by H. William Welliver III 21 Mar '15

21 Mar '15

Hi- I was suggested that it might be a good idea to do a test release of 8.0. I think that’s a pretty good idea. I was wondering if anyone had any thoughts about who might be expected to prepare that release. I’m happy to help but don’t want to automatically assume I’d be the one. Bill

3 2

Unexpected and unused calls to resolv()
by Chris Angelico 18 Mar '15

18 Mar '15

See attached test-case: run main.pike. When a function is defined in a file, I would normally expect that resolv() is not called. But if the function definition is below the usage, resolv() is called, but the result seems to be ignored; the code uses the function from elsewhere in the file. (Note that above() is never retrieved in that way.) This normally wouldn't be a problem, but I use the resolv() calls to detect dependencies, and this oddity was resulting in a file being purportedly dependent on itself. (Was able to deal with that by reordering code, fortunately.) Any idea why this happens? Is it intended behaviour? ChrisA

1 0

=> Lambda shorthand syntax
by Stephen R. van den Berg 16 Mar '15

16 Mar '15

Has anyone ever considered adding support for the => shorthand lambda operator to Pike? It's available in several languages. The docs for C# are here: https://msdn.microsoft.com/en-us/library/bb397687(v=vs.110).aspx -- Stephen.

5 8

Re: => Lambda shorthand syntax
by Ralph Ritoch 14 Mar '15

14 Mar '15

A macro also works for shorthand... #define f(x, y ...) lambda(y) { return x; } int main() { function y = f(x * x, mixed x); write((string)y(5)); } Best Regards, Ralph Ritoch On Sat, Mar 14, 2015 at 7:50 PM, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum <10353(a)lyskom.lysator.liu.se> wrote: > If you want x to be mixed, you should declare it as such. That is the > rule everywhere else. >

1 0

Re: => Lambda shorthand syntax
by Stephen R. van den Berg 14 Mar '15

14 Mar '15

Ralph Ritoch wrote: >I don't see it in the documentation but pike already has a syntax for >lambda expressions. Yes, it does. >Good luck with the pursuit for more operators. It's a new shorthand that makes certain common lambda expressions more readable (and is popular in other languages). -- Stephen.

1 0

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 March 2015