Pike-devel

pike-devel@lists.lysator.liu.se

3041 discussions

proposed backport from 7.9 to 7.8
by Bill Welliver 18 Jul '12

18 Jul '12

I've made a number of commits to 7.9 surrounding the external module support tools (monger and pmar_install) that I'd like to include in the next 7.8 release. Also, I'd like to backport the fixes and additions to spawn_pike and the new get_user/get_home functions (but not FreeConsole and friends) in System as well. The code is fairly well isolated and don't think there will be any downside. Considering the utility of the functionality and that 7.9 is likely to be in development for the foreseeable future, I think it's worth doing. Does anyone have any objection? Bill

3 2

New Pike Beta: 7.8.694
by H. William Welliver III 12 Jul '12

12 Jul '12

I've made a new beta build which for your consideration. If no problems are found, this build will become the next stable release. Please download, build, test, make binary packages, etc. As always, please report back with any problems (or successes, too!) http://pike.ida.liu.se/download/pub/pike/beta/7.8.694/ Best, Bill

8 24

Pike type regression
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 11 Jul '12

11 Jul '12

nilsson@riaa:~/pike$ make run_hilfe ARGS="-V7.6" Configure arguments: Use `make CONFIGUREARGS="..." ...' to change them. They will be retained in the build directory. Making run_hilfe in build/linux-3.0.0-22-generic-x86_64 /home/nilsson/pike/build/linux-3.0.0-22-generic-x86_64/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/nilsson/pike/build/linux-3.0.0-22-generic-x86_64/master.pike -V7.6 Pike v7.9 release 5 running Hilfe v3.5 (Incremental Pike Frontend) (running in Pike 7.6 compat mode) > Calendar.Events; make[2]: *** [run_hilfe] Segmentation fault make[1]: *** [_make_in_builddir] Error 2 make: *** [run_hilfe] Error 2 (perhaps I should get a bugs.roxen.com account again...)

1 0

roxen.c
by Martin Nilsson (Opera Mini - AFK!) ＠ Pike (-) developers forum 07 Jul '12

07 Jul '12

When not to use dash as punctuation :) i = -i; /* Always defined for unsigned - signed overflows are not. */

1 0

encoding of huge constants
by Arne Goedeke 02 Jul '12

02 Jul '12

Precompilation is currently (in 7.9) compiling things like array const = enumerate(100000000); into the .o files. This happens in the new Foreach* benchmarks. It gives me files that are around 40mb in size, and the decoding probably takes much more time than would compiling and running this once. I have no idea how to fix this. It seems logical that this happens, but was it always like this? Arne

1 1

Final feedback for 7.8.686
by H. William Welliver III 29 Jun '12

29 Jun '12

It's been about 2 weeks since I cut a new 7.8 release candidate and I haven't heard much feedback, good or bad. Since there weren't many problems with the previous release, I'm going to assume that everything is okay. However, if anyone has any feedback, please let me know, as I plan to mark it as an "official release" build. Assuming all goes well, what are the changes that a Windows build and friends can be ready in the near future? I tried doing a build, but I think things have moved on (at the time, using VC6 worked, etc) since my last Windows build adventure. Best, Bill

4 3

ZIP file program loader
by Bill Welliver 21 Jun '12

21 Jun '12

When I was in Sweden last fall, I remember having a brief conversation with someone who'd written a resolver that loads classes or modules from a tar or zip file (the details are a little hazy). Does that sound familiar to anyone here? If so, do you have any code you might be willing to share? Bill

4 7

USB.devices OneWire.devices, how to unite it into an IO module?
by Stephen R. van den Berg 14 Jun '12

14 Jun '12

I currently have a functioning usblib module, and for now it lives in src/post_modules/USB in my personal tree. I am now embarking onto creating a OneWire module/class which uses the aforementioned USB lib to actually communicate with the 1-wire busmaster. The question is, where do I put all these modules. Most logical would be under a module named IO, so it would become IO.USB.devices and IO.OneWire.devices or somesuch. Then again, the USB module is completely written as a cmod. The OneWire module might live as a Pike module. How do I solve the namespace problem, I'd like to unite them under master module IO? Renaming the USB module to _USB, then inheriting the module under lib/modules/IO.pmod again might work, but gets messy with autodoc, since I'd like to keep the documentation in the cmod file itself. Any suggestions? -- Stephen. How many weeks are there in a lightyear?

8 32

New Pike Beta: 7.8.686
by H. William Welliver III 13 Jun '12

13 Jun '12

1 0

Pike 7.8 Release (last call)
by H. William Welliver III 12 Jun '12

12 Jun '12

Does anyone have any objections to 7.8.680 becoming the next official release of Pike? Do note that machine code is non-functional on (at least more modern instances of) i386. If I don't hear any objections in 24 hours, I will attempt to update the website, etc, with the new information. Best, Bill

9 18

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